> 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/site-installation/card-types/setting-up-card-types/pins-tab.md).

# PINs tab

1. Click the **PINs** tab.

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

   This screen enables you to define whether PINs are enabled or disabled for the card type. If you choose not to use PINs, when cards of this type are encoded a user defined PIN cannot be entered by the operator.
2. If you want to use PINs, check the **Use PINs** checkbox and set the Minimum PIN length.

   (Default = 4 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 for this Card Type.
   * The maximum PIN length is 8 digits. There is no mechanism to reduce the maximum size. Hence if a site sets minimum at 4, the user can enter PIN length anywhere from 4 to 8 digits.


---

# 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/site-installation/card-types/setting-up-card-types/pins-tab.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.
