> 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-workspaces/working-with-a-cardholder.md).

# Working with a cardholder

Selecting a cardholder opens their properties across the tabs below. Changes save automatically or when you select Done. A confirmation appears in the bottom-right corner: a green tick if the change saved, or a red cross with the reason if it failed.

<table><thead><tr><th width="152">Tab</th><th>What it is for</th></tr></thead><tbody><tr><td>Activity</td><td>Read-only list of the cardholder's last 25 events, newest first. Matches the Event Trail on the <strong>Cardholder</strong> Viewer. Requires the "View Events" privilege.</td></tr><tr><td>History</td><td>Read-only list of the latest 30 changes to the cardholder. Use the date range filter to narrow it. Operators without the "View Events" privilege see this tab only while the <strong>Show History Tab</strong> setting is turned on in <strong>Settings</strong>.</td></tr><tr><td>Access</td><td>Shows the cardholder's Access Groups with <strong>status</strong>, (i.e. Active, Pending or Expired), and <strong>From/Until dates</strong>. Remove access, or select <strong>Assign Access</strong> to add groups, copy another cardholder's groups, adjust dates and fill in required PDFs in one step.</td></tr><tr><td>Credentials</td><td>Cards and credentials with number, type, issue level, status and dates. Change a credential's state, or select Assign Credential to add one. Printing and encoding are not available.</td></tr><tr><td>Competencies</td><td>Assign competencies and set expiry dates. Shown only if competencies are configured, or the cardholder already has one you can view.</td></tr><tr><td>Details</td><td>Basic details and Personal Data Fields, with validation. Use <strong>Set User Code</strong> to assign a user code.</td></tr></tbody></table>

The left panel panel shows the cardholder's photo, name and authorised status, along with their division, last zone entered and notes. The tabs along the top give access to the cardholder's activity, history, access, credentials, competencies and details.

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

<details>

<summary>Assigning access</summary>

1. Open the cardholder and select the **Access** tab, then select **Assign Access**.
2. In the Assign Access panel, use the **Search Access** tab to find access groups, or the **Copy Access** tab to copy another cardholder's access groups. Use the division filter to narrow the list.
3. Tick the access groups to assign. Each one appears on the right.
4. Optionally, set the **From** and **Until** dates for each access group.
5. Select **Next**, then complete any required Personal Data Fields (additional information) on the following step.

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

</details>

<details>

<summary>Assigning a credential</summary>

1. Open the cardholder and select the **Credentials** tab, then select **Assign Credential**.
2. In the panel that opens, choose the credential **Type** from the drop-down.
3. Fill in the **Details**. The fields shown depend on the credential type.
4. Select **Done**.

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

</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/configuring-command-centre/administration-workspaces/working-with-a-cardholder.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.
