> 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/working-with-viewers/tile-actions/cardholder-cards-tile-actions/viewing-pins.md).

# Viewing PINs

There are two types of PINs, (i.e. System Generated PINs and User Defined PINs). An operator with "View PINs" privilege can view PINs assigned to cards according to the following rules:

**Note:** The **View PIN** button is disabled and does not work if the **View new PINs on first use at configured HBUS Terminals** checkbox is ticked (on the **NPSA** sub-tab of the Server Properties **Standards** tab).

* An operator can only see User Defined PINs if they have the "View PINs" privilege AND the **Store PINs for later viewing** checkbox is checked on the Server Properties **Card Security** tab (in the Configuration Client).
* An operator can see System Generated PINs if they have the "View PINs" privilege AND the PIN has not been changed. If changed it then becomes a User Defined PIN and the rule above applies.
* User Defined PINs changed prior to the **Store PINs for later viewing** checkbox being checked (on the Server Properties **Card Security** tab) are not retrievable and will need to be reallocated if the cardholder has forgotten it.

To view a PIN:

1. Click the **View PIN** button.

   The View PIN pop-up displays showing the User PIN.

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

   **Note:** If the PIN has not been stored and encrypted (via the setting in the Server Properties), the following message will display on the View PIN pop-up rather than the User PIN:

   *"The PIN for this card is not stored in a retrievable form."*
2. Click the **Close** button.

   The View PIN pop-up closes.


---

# 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/working-with-viewers/tile-actions/cardholder-cards-tile-actions/viewing-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.
