> 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-history-tile-actions.md).

# Cardholder History Tile actions

The Cardholder History Tile is "read-only" and shows Audit history details for a Cardholder.

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

The following operator privileges are required:

* "View Cardholders",
* "View Mobile Credential Email and Mobile" (to see mobile credential changes),
* "View Cardholder Notes" (to see changes to notes), and
* "View Operators" (to see changes to operator configuration).

The entries on this Tile display in tree view, and each entry represents one change made to the cardholder. They are sorted by time, in descending order, with the latest change at the top. The titles of the entries show when the change was made and what the change was. Extra information is sometimes included in the titles to make a change identified easily, (e.g. when a card was created, the card number and card type are included in the title).

<details>

<summary>Viewing details for an entry</summary>

Click the arrow head beside an entry to expand the list of items below it.

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

The first item under the entry shows the operator who made the change, and the workstation where the change was made.

All the other items that follow show the details of the change.

</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-history-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.
