> 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/assigning-pins.md).

# Assigning PINs

If the CipherToken Card Type was configured to use PINs (in the Configuration Client), the **Assign PIN** button will be enabled.

1. Click the **Assign PIN** button.

   The Assign PIN pop-up displays.

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

   * Manually type a PIN number into the first **User PIN** field, and then confirm it by repeating it in the second **User PIN** field, OR
   * Click the **Generate PIN** button to automatically generate a random PIN.

     **Note:** Generated PINs will only display while the Assign PIN window is open. Once closed, there will be no way of re-viewing the PIN number since the PIN itself is not stored. Generated PINs will be of length equal to the minimum PIN length set against the CipherToken Card type.

   **Note:** The system prevents PINs with 3 consecutive or 3 repeating numbers from being either manually entered or automatically generated.
3. Click the **OK** button.

   The Assign PIN pop-up closes.
4. Click the **Save** button.


---

# 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/assigning-pins.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.
