> 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/creating-a-card-state-set.md).

# Creating a Card State Set

Perform the following procedure to create a new Card State Set:

1. Click the **New Card State Set** button on the Viewer Navigation Panel.

   The new Card State Set is added to the Viewer Navigation Panel, and the Card State Configuration pop-up displays.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-bddfe2a02c9beac025956c9a46b9b6901ee80615%2Fcardstateconfig_popup.png?alt=media)
2. If you want to replace the default name the system has given the Card State Set, enter a new name in the **Name** field (limited to 60 characters).
3. If required, enter a logical **Description** (limited to 200 characters).
4. The **Division** button defaults to the name of the last Division in which the Operator created a Command Centre item, regardless of whether it was created in Configuration Client or via Command Centre Client.

   If this is not the appropriate Division for this Card State Set, select a Division as follows:

   1. Click the **Division** button.

      A browse tool displays.

      ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-7b199073d021ca11902823b748c96d639d5d5f0f%2Fselectdivision_browsetool.png?alt=media)
   2. Select the appropriate Division.
   3. Click the **OK** button.

      The pop-up closes and the button changes to the name of the Division you selected.

      **Note:** If you have not set up Divisions yet, you can add these to your Card State Set at a later stage.
5. Click the **Close** button.

   The Card State Configuration pop-up closes.

   There are two tabs, (i.e. **Card States** and **History/Notes** ). The **Card States** tab displays by default.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-a7779d1bc4da45b028ed78dd1c1036202f416cac%2Fcardstates_cardstatestab.png?alt=media)
6. Change the **Initial Card State** if required, by selecting another one from the drop-down list.
7. Add and remove Card State(s) as required for this Card State Set. See [Adding States to a Card State Set](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/card-states/adding-states-to-a-card-state-set.md) and [Removing States from a Card State Set](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/card-states/removing-states-from-a-card-state-set.md) for the procedure.
8. Indicate whether a custom card state is available for selection on the Cardholder Cards tile.

   States available for selection are indicated by a "tick" and are made by clicking in the checkbox in the **Available for use** column.

   **Note:** By default, all custom card states are available for selection.
9. Change any of the custom card states to **Permanently Disabled** if required.

   **Note:** 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).
10. If you want to record any note(s) about the Card State Set, click the **History/Notes** tab.

    Refer to [History/Notes tab](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/generic-administration-tasks/history-notes-tab.md) for further detail.
11. Click the **Save** button.

    A new Card State Set has been created.

### Hints

{% hint style="info" %}
**Editing and Deleting Card State Sets**

Refer to [Editing items](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/generic-administration-tasks/editing-items.md) and [Deleting items](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/generic-administration-tasks/deleting-items.md) for procedures on how to edit and delete Card State Sets.

**Note:** A Card State Set cannot be deleted if it is assigned to a Card Type.
{% endhint %}

{% hint style="info" %}
**Duplicating Card State Sets**

Operators privileged to create card state sets can also duplicate card state sets, which makes the task of setting up multiple card state sets that are very similar much quicker.

Refer to [Copying items](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/generic-administration-tasks/copying-items.md) for the procedure.
{% 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/creating-a-card-state-set.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.
