> 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-a-user-code-for-terminal-access.md).

# Configuring a User Code for Terminal Access

### Introduction

This procedure describes how to specify a user code for a Cardholder, in order to identify the Cardholder at an HBUS Terminal or HBUS Alarms Only Terminal.

Operators require the “Edit Cardholders” operator privilege, and must be in the same or a parent Division of the Cardholder. Without this operator privilege the fields on this tab will not be enabled.

**Note:** User Codes can also be used as PINs for any reader with a keypad. This is set via a checkbox on the **Advanced** tab of the reader properties.

### 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 the **Cardholder** you wish to give a user code to.
3. **Double-click** the mouse button.
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-8 digit user code in the **User code** field.

   **Notes:**

   * As you enter the user code, asterisks display in place of each digit.
   * Command Centre enforces a user code range of 1 to 99999999. Therefore the code must contain at least one non-zero digit, (i.e. 0000 or 00000000 are invalid and an error will be generated).
6. Confirm the user code by re-typing it in the **Confirmation** field.
7. Click **Apply**.

### Result

A user code has been specified to identify a Cardholder at an HBUS Terminal or HBUS Alarms Only Terminal.


---

# 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-a-user-code-for-terminal-access.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.
