> 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/configuration-client/licensable-features/ciphertoken-card-support/enrolling-a-ciphertoken-configuration-card.md).

# Enrolling a CipherToken configuration card

### Introduction

A CipherToken Card Type needs to be configured in the Configuration Client to be able to assign CipherToken cards to Cardholders.

**Notes:**

* There is no limit to the number CipherToken card flows and card types a site can have.
* The "Manage Keys" operator privilege is required to read the configuration card.
* The configuration data includes the keys that are required to validate the next configuration card if the site keys ever need to be rolled.

### Configuration

To configure a CipherToken Card Type, perform the following procedure in Gallagher Configuration Client:

1. Click **Configure** from the menu bar, then **Card Types**.

   The **Card Type** List Window opens.
2. **Right click** and select **New…CipherToken Card Type**.

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

   By default the **General** tab displays.
3. Complete the fields as required.

   For further detail see [General tab](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/general-tab.md).
4. Click each tab in turn and configure the CipherToken Card Type as required:

<details>

<summary>Setup tab</summary>

1. Click the **Setup** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-a03cbe10bde97be7de9a6455eafe29290239265b%2Fciphertokencardtype_setuptab.png?alt=media)
2. Select the appropriate **Card State Set** (if only one exists it will default) to be associated with this CipherToken card type, from the drop-down box.

   **Note:** Once the Card State Set is assigned to the CipherToken Card Type and saved, it cannot be changed.
3. If you want to use PINs, check the **Use PINs** checkbox and set the **Minimum PIN length**.

   (Default = 6 digits. Range = 4 - 8 digits)

   **Notes:**

   * If you do not choose to **Use PINs**, the **Assign PIN** button on the Cardholder Cards tile in Command Centre Client will be disabled
   * The maximum PIN length is **8** digits. There is no mechanism to reduce the maximum size. Hence if a site sets minimum at 6, the user can enter PIN length anywhere from 6 to **8** digits.

</details>

<details>

<summary>Inactivity tab</summary>

1. Click the **Inactivity** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-b0cd86fb450ec892ede7499f664f7a298cf2dac5%2Fciphertokencardtype_inactivitytab.png?alt=media)
2. Do you wish to enable the Inactive Card Expiry feature?

   **Note:** All cards of a particular type shall share a common inactivity timeout if enabled.

   <table><thead><tr><th width="75">If...</th><th>then...</th></tr></thead><tbody><tr><td>yes,</td><td>check the <strong>Disable Inactive Cards</strong> checkbox. Go to Step 3.</td></tr><tr><td>no,</td><td>leave the <strong>Disable Inactive Cards</strong> checkbox unchecked. Go to Step 5.</td></tr></tbody></table>
3. Enter a figure to represent the number of days of inactivity that will disable a card.

   **Notes:**

   * When this feature is first enabled the default timeout = 30 days. The range is 1-999 days.
   * If you set a card type to disable after 1 day of inactivity, these cards will become disabled 24 hours to the second after the **Apply** button is clicked, (e.g. card type set on 27/01/2022 at 16:10:15; if not used these cards become disabled on 28/01/2022 at 16:10:15).
   * Cardholders will be expired regardless of activity if card activity events are not configured to log events throughout the site. (Refer to Event Defaults for further detail.)

</details>

5. Click the **Custom Fields** tab if you want to add and assign a custom field value to the CipherToken Card Type.

   For further details regarding the **Custom Fields** tab, see [Custom Fields](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/custom-fields.md).
6. Click the **Notes** tab if you want to add a note(s) about the CipherToken Card Type.

   For further details regarding the **Notes** tab, see [Notes](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/notes.md).
7. Click **OK** to close and save your changes.

   Click **Cancel** to close without saving your changes.

   Click **Apply** to save your changes and stay in this window.

### Result

A CipherToken Card Type has been created.

**Note:** Once the configuration is saved it cannot be edited.


---

# 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/configuration-client/licensable-features/ciphertoken-card-support/enrolling-a-ciphertoken-configuration-card.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.
