> 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/licensable-features/ciphertoken-card-support/ciphertoken-cards-in-command-centre/enrolling-ciphertoken-cards.md).

# Enrolling CipherToken cards

To assign and activate a Cardholder CipherToken card, perform the following procedure in Gallagher Command Centre Client:

**Note:** CipherToken Cards can also be assigned to Visitors through Visitor Management or Visitor Management Kiosk.

1. From the Cardholder Viewer, locate the Cardholder you want to assign a CipherToken card to.
2. On the Cardholder Cards tile, click the **Assign Card** button.
3. From the **Card Type** drop-down list select the CipherToken Card Type.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-884fcbf33b8c135d8c10551c43de25fa3b8eec02%2Fciphertoken_assigncardpopup.png?alt=media)
4. The **State** indicates indicates the status of the CipherToken Card Type.

   Select the appropriate **State** from the drop-down list.

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

   The state defaults to the Initial Card State as defined in the Card State configuration, and can be set to any other available state in the drop-down list.
5. Configure the **Number**, **From** and **Until** fields as appropriate.
6. Click the **OK** button.

   If valid, the **Assign Card** pop-up will close and the card will appear in the grid in the Cardholder Cards tile.
7. To display site information for the CipherToken Card Type, click on the arrowhead to the left of CipherToken Card Type.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-2fe5d333ceeda6730dc81e26176ac4a371b7458e%2Fciphertoken_chcardstile.png?alt=media)
8. Click the **Save** button.

   **Note:** The **History** tab of a cardholder’s properties (in Configuration Client) will also show what has been set during enrolment.


---

# 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/licensable-features/ciphertoken-card-support/ciphertoken-cards-in-command-centre/enrolling-ciphertoken-cards.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.
