> 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/using-command-centre/working-with-viewers/tile-actions/cardholder-relationships-tile-actions.md).

# Cardholder Relationships Tile actions

The **Relationships** tab on this tile displays any Cardholders and their Roles that this Cardholder reports to.

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

The **Roles Held** tab is "read-only" and is populated with the Role(s) this Cardholder performs and the Cardholders who report to them in each Role.

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

Columns on the Cardholder Relationships Tile can be resized and/or reordered if required. See below for further detail.

<details>

<summary>Resizing/reordering columns</summary>

It is possible to resize and/or reorder columns on any of the Administration Viewer Panels and some tiles if required, as follows:

<table><thead><tr><th width="126">To...</th><th>Steps</th></tr></thead><tbody><tr><td>reorder columns</td><td>Click on the column tile and drag it to the required position.</td></tr><tr><td>resize columns</td><td><ol><li>Hover over the column divider until the mouse pointer changes to a "double-ended arrow".<br><img src="https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-7ca7c1c062c2f40f24571968c0c20565b4351b89%2Fresize_macrocolumn.png?alt=media" alt=""></li><li>Click and hold down the mouse button.</li><li>Move the mouse in the required direction until the column is the required size.</li></ol></td></tr></tbody></table>

</details>

### Operator Privileges

<table><thead><tr><th width="214">To...</th><th>you need...</th></tr></thead><tbody><tr><td><strong>view</strong> cardholder relationship assignments for a cardholder,</td><td><p>one of the following privileges in the division of the cardholder for whom the relationship assignments are being viewed:</p><ul><li>"View Cardholders"</li><li>"Edit Cardholders"</li><li>"View Cardholder Notes"</li><li>"Edit Cardholder Notes"</li><li>"Edit Cardholder Notification"</li><li>"Print/Preview &#x26; Encode Card"</li><li>"Delete Cardholders"</li></ul></td></tr><tr><td><strong>assign</strong> a relationship to a cardholder,</td><td>the "Edit Cardholders" privilege in the division of the cardholder.</td></tr><tr><td><strong>remove</strong> a relationship from a cardholder,</td><td>the "Edit Cardholders" privilege in the division in which the cardholder to whom the relationship is assigned is stored.</td></tr><tr><td><strong>see</strong> an individual Role,</td><td>the "View Cardholders" OR "Edit Cardholders" privilege in the division of the Role.</td></tr><tr><td><strong>see</strong> a cardholder to assign to a Role,</td><td>the "View Cardholders" OR "Edit Cardholders" privilege in the division of the cardholder to be assigned.</td></tr></tbody></table>

**Note:** It is not possible to edit a Relationship. Instead, the Relationship must be removed and a new one assigned.

### Tile Actions

<details>

<summary>Assigning Relationships</summary>

1. Click the **Assign Relationships** 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)
2. 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.
3. 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.
4. 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.
5. From the search results, click on the Cardholder you want to assign to this Role.
6. Click the **OK** button.

   The pop-up closes and the Role and Cardholder assigned to that Role now appears on the Cardholder Relationships tile.

   **Note:** If you decide to cancel this change, the **Revert to Saved** button allows you to do so before saving it.
7. Click the **Save** button.

</details>

<details>

<summary>Removing Relationships</summary>

1. Select the Relationship you want to remove.
2. Click the **Remove** button.

   The selected Relationship is removed from the Cardholder Relationships Tile.

   **Notes:**

   * If you decide to cancel this change, the **Revert to Saved** button allows you to do so before saving it.
   * Multiple Relationships can be removed in a single action.
3. Click the **Save** button.

</details>


---

# 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/using-command-centre/working-with-viewers/tile-actions/cardholder-relationships-tile-actions.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.
