> 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/understanding-card-states.md).

# Understanding Card States

Custom card states go beyond the traditional states of Active, Expired and Disabled. Custom Card State configuration allows operators to track and report on Lost, Stolen and Damaged cards (default custom states), as well as pending, suspended, on-hold or any other required card state.

Card assignment, removal, issue-level and state changes are written to the card history and this history can be reported on using Cardholder and Activity reporting, to provide audit information on card changes. Card State history also provides enhanced security ensuring cards are not reproduced when lost or stolen cards exist outside the premises.

### Card State Set assigned to a Card Type

Card State Sets get assigned to the properties of a Card Type (on the **Setup** tab), in Configuration Client. Once assigned and saved the set cannot be changed for the Card Type. Bulk changes can be used to change the Card Type if an alternative set of states is required.

### Multi-server systems

In a multi-server system the following applies for Card States:

* Card states and their properties need to be replicated in a multi-server environment, so that card states configured in a local server are available to use at a remote server.
* Custom card state assignments need to be replicated, (e.g. A card that is marked as Lost on one server will need to replicate to other servers).
* Multi-server Card State conflicts raise alarms.


---

# 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/understanding-card-states.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.
