> 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-management/cardholders/configuring-user-codes-for-access-at-card-readers-with-keypads.md).

# Configuring User Codes for access at Card Readers with keypads

### Introduction

User codes can be configured, in place of PINs, for gaining access at card readers with keypads, (i.e. Gallagher readers and third party readers that are supported by Command Centre).

### Restrictions

* "Code or Card - PIN" mode does not work for User Code only mode. The Access Zone's mode must be "Code or Card - No PIN" for this feature to work correctly.
* This feature does not support duress functionality.
* The Access Zone's Code Only code will not allow access when the reader is configured with "PIN is user code" enabled. Access can only be granted by User Code entry or a valid Card.
* The maximum length User Code accepted is 6 digits.
* Double card overrides are not supported.

### Procedure

1. Click **Manage** from the menu bar, then **Cardholders**.

   The **Cardholder** List Window opens (in [grid view](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/grid-view.md)).
2. Highlight a Cardholder that requires access via the Reader.
3. **Right-click** and select **Properties**.
4. Click the **User Code** tab.

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

   **Note:** This code will be hidden from all operators, regardless of privilege.
5. Enter a 4-6 digit user code in the **User code** field.

   **Notes:**

   * As you enter the user code, asterisks display in place of each digit.
   * The code must contain at least one non-zero digit, (e.g. 0000 is invalid and an error will be generated).
6. Confirm the user code by re-typing it in the **Confirmation** field.
7. Click the **OK** button.
8. Repeat Steps 2 - 7 for each Cardholder that requires access at the Reader.

   **Note:** You can find out which Cardholders have user codes by running a summary Cardholder Report and selecting the User Code field. While the report will indicate who has a user code, the actual codes will not be disclosed.
9. Click **Configure** from the menu bar, then **Hardware**.

   The **Hardware** List Window opens.
10. **Right click** on the reader and select **Properties**.
11. Click the **Advanced** tab.

    ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-363b431cc139850a5a302ed48b9134eb4c035102%2F3rdpartyreader_advancedtab.png?alt=media)
12. Check the **PIN is user code** checkbox.

    With **PIN is user code** checked, the user code will be required in place of a PIN for any transactions at the reader which would normally require a PIN. This includes door access and overrides.

    **Note:** Double-card overrides do not work in this mode, therefore leave the Double card overrides as **Disabled**.
13. Click the **OK** button.
14. Set the access mode of the reader's Access Zone to "Code or Card - No PIN". This can be done from either the:
    * **Schedule**. See [Creating a new Schedule](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/schedules/creating-a-new-schedule.md) for further detail.

      The Schedule is then applied to the Access Zone via the **Access Mode** tab of the Access Zone properties.
    * **Access Zone**, as follows:

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

      1. On the **Status and Overrides** tab, select the **Access Mode** tab.
      2. Select the "Code or Card - No PIN" mode from the drop-down list.
      3. Click the **Override Now** button, and then the **OK** button.

### Result

User codes have been specified to identify cardholders at a Reader for PIN only access.

When cardholders enter their user code correctly at the Reader, the following Door Access Granted event will be generated in Command Centre:

*"\[Cardholder] was granted entry into \[Access Zone] through \[Door]"*


---

# 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-management/cardholders/configuring-user-codes-for-access-at-card-readers-with-keypads.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.
