> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/bulk-changes/creating-a-new-cardholder-bulk-change/relationships.md).

# Change Relationships

1. Select **Relationships**.

   The Change Relationships pop-up displays.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-fe67baf7c84b26c6b84c49c10a0742083fc80445%2Fchangerelationships_popup.png?alt=media)
2. Do you want to add or remove Relationships for the cardholders?

   If **remove**, go to Step 8.

   If **add**, click the **Assign Relationship** button.

   The Assign Relationship pop-up displays.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-b9d5923da70bd9564232f3c4a0ba99a6f5a19b18%2Fassignrelationship_popup.png?alt=media)

   **Notes:**

   * If the Bulk Change action is to 'add' a relationship record to a cardholder for a Role that is already filled, then the result will effectively be a change to the cardholder held against the role.
   * All Roles added to a cardholder, must be accompanied with a populated cardholder filling that role, (i.e. a Role cannot be added that is 'blank').
3. Click on the **Select Role** drop-down list, and select the required Role.

   The drop-down list is populated with all Roles configured in Configuration Client.
4. To find the Cardholder that you want to assign to this Role, select what criteria you want to search on from the **By** drop-down list, (i.e. Name, Description, Division, Card Number or All).

   By default, Name is selected.
5. Start entering characters in the **Search** field.

   A minimum of 3 characters starts the search. However, if you selected Card Number(s) as the search criteria, you need to click the ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-f1056e058547589bcd63a07bc872a1a741ea174c%2Fsearchbutton.png?alt=media) button after you enter a number in the **Search** field.
6. From the search results, click on the Cardholder you want to assign to this Role.
7. Click the **OK** button.

   The pop-up closes and the Role, and Cardholder assigned to that Role, now appears on the Configure Relationships pop-up.
8. Select the Relationships that need removing from the cardholders by clicking the **Select Roles** button in the "Remove these Relationships" section.

   The Select Roles pop-up displays.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-d37eb657c47ff293ed8bf135689e5586b6b294bc%2Fselectroles_popup.png?alt=media)
9. Click the checkbox next to each Role name you want to remove, or click the **Select All** button if you want to remove all Roles.
10. Click the **Add Selection** button.

    The pop-up closes and each of the selected Role(s) now appears on the Configure Relationships pop-up.
11. Click the **OK** button.

    The Change Relationships pop-up closes.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/bulk-changes/creating-a-new-cardholder-bulk-change/relationships.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
