> 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/quick-tips-for-working-with-card-states.md).

# Quick Tips for working with Card States

* Sites can define custom card states so that a card can be recorded as Lost, Stolen, Damaged or another custom-defined state, instead of using the traditional states of Active, Expired and Disabled.
* Card States with unsaved changes display in the Navigation Panel in **bold** and have a **\*** at the end of their name.
* Once a Card State Set is assigned to a Card Type (on the **Setup** tab in Configuration Client) 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.
* The **Active** and **Disabled (manually)** states cannot have their attributes changed, (i.e. they are always available and cannot be made a permanently disabled state).

### More information

For more information, refer to the topic *"Card States"* in the Gallagher Command Centre Online Help.


---

# 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/quick-tips-for-working-with-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.
