> 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/card-states/configuring-a-card-state-history-report.md).

# Configuring a Card State History Report

A privileged operator can utilise the Cardholder Report structure to report on Card History. When one or more of the Card History columns is added to a Cardholder Report, along with Cardholder Name column(s), then the report will include a row for each card assignment, state change, issue level change and removal. The report is filterable by Historical Card Status and Historical Card Status Time.

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

### Hints

{% hint style="info" %}

* Use of other card filters will not restrict the report at the historical card level, rather at the cardholder level. Hence it is recommended not to use Card Type or Card Number filters.
* If required, use any other Cardholder filter to restrict the cardholders returned in the report, (e.g. Cardholder Personal Data Field filter).
  {% endhint %}


---

# 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/card-states/configuring-a-card-state-history-report.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.
