> 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/adding-a-card-to-a-cardholder.md).

# Adding a Card to a Cardholder

### Introduction

A card is an access token. The cardholder presents the card to a reader to gain access to a zone or elevator level.

One cardholder may be issued with more than one card; for example, they require access to different sites.

**Note:** The default limit is 500 cards per cardholder.

### 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. Locate, and highlight, the Cardholder to edit.
3. **Right click** and select **Properties**.
4. Click the **Cards** tab.

   The **Cardholder Authorised** checkbox is ticked by default. This authorises the cardholder so they can use their cards. This is not specific to one card - it authorises the use of all cards listed.
5. **Right click** anywhere within the upper grid, (i.e. on a column header, on the scroll bar, in the blank area or on a card if there is one), and select **Insert**.

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

   A "new card" is added to the upper grid and highlighted. This new card is enabled and if it has had card defaults already configured, (see [Setting up Card Types](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/card-types/setting-up-card-types.md)), the 'From', 'Until' and/or 'Issue Level' fields will be populated with those defaults. The card will also be allocated the next available 'Number'.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-1f72a6dc3ebe4a2becfde1eb02c2944674e1dbbe%2Fcard_inserted.png?alt=media)
6. Is the "new card" the required Card Type?

   <table><thead><tr><th width="74">If...</th><th>then...</th></tr></thead><tbody><tr><td>yes</td><td>go to Step 8.</td></tr><tr><td>no</td><td>click the <strong>Card Type</strong> drop-down menu box and select the correct Card Type. For example, proximity card, mag-stripe card, etc.<br><br><strong>Note:</strong><br>The default settings will change to that of the card type selected.</td></tr></tbody></table>
7. Set the remaining card details.

   **Note:** If the 'From', 'Until' and/or 'Issue Level' fields are populated with default settings, they can be overwritten if required. The card number can also be overwritten prior to saving changes on this screen.

   **Card State**

   Each card requires a current state. The state selected initially is configured from the Card Type's Card State Set, and the drop-down will be populated with all the card states that are available for use.

   **Number**

   Each card requires an encoded number to uniquely identify it. Once you click **Apply** the card number becomes greyed out and can not be altered. The card number range that can be assigned to a card type is set in the Card Type properties. The card number format of the selected card type will determine what characters can be used, as follows:

   <table><thead><tr><th width="150">If the card type is...</th><th>then...</th></tr></thead><tbody><tr><td><strong>Decimal</strong> format,</td><td>a decimal card range is supported. The system "auto-allocates" a card number, however this can be overwritten if required by typing another number over the one allocated prior to saving changes on this screen.</td></tr><tr><td><strong>Text</strong> format,</td><td><p>if a regular expression syntax string has been configured in the Card Type properties, you will be forced to enter a card number that fits that definition.<br><br><strong>Notes:</strong></p><ul><li>a maximum of 251 alphanumeric characters are supported. However, with some languages this may be less as some characters use more than one byte.</li><li>If you enter an invalid card number, an error message will display indicating it is invalid, and show what the syntax string pattern is.</li></ul></td></tr></tbody></table>

   **From**

   Set the date and time the card will be activated - the Command Centre system will accept the card details when presented.

   Note:

   If you do not enter a date in the "From" field, when a cardholder is issued a card of this type and the card is enabled, activation will be immediate.

   **Until**

   Set the date and time the card will expire - the Command Centre system will not accept the card after this date.

   Note:

   If you do not enter a date in this field, the card will not expire.

   **Issue level** (1 to 15)

   If a card is replaced, you do not need to go through the process of creating a new card; you can simply increment the issue number.

   A card may need to be replaced if the cardholder has lost their card, for example.

   **Resident**

   Check this box if you require the details of this cardholder to be stored (resident) at the Controller.

   The Controller stores a 'resident' cardholder and security parameters database to enable it to carry out access control and security functions. The cardholder database stores access data for cardholders who will regularly use the devices attached to that Controller. It enables the Controller to make access control decisions instantaneously.

   For cardholders that are not included in the resident cardholder database, when they present their card, the Controller requests access information from Command Centre. Their information is then stored on the resident database, but may get discarded if the Controller Cardholder database becomes full and another unknown user presents their card. If communications fail and the cardholder information is not in the Controller, that cardholder will not be able to gain access.

   **Trace**

   A message and/or alarm is generated each time the card is presented to a reader, including readers that are associated with *Remote Arming Terminals*.

   **Last Printed/Encoded**

   A read-only field displaying the "Last Printed/Encoded" information, (i.e. the date last printed and/or encoded, and the Issue Level used), for the currently selected card.
8. Click **OK** to exit and save your changes.

   Click **Cancel** to exit without saving your changes.

   Click **Apply** to save your changes and stay in this window.

   **Notes:**

   * When you save changes at this stage, depending on the expiry date set for the card, a "card activated" or "card expired" event may be logged in the **Event** window.
   * Once you save your changes the Card Type and Number fields become greyed out and can not be changed.

### Result

The new card details are updated to reflect the changes you have made.

### Hint

{% hint style="info" %}
There cannot be two cards in the system with the same card number *and* the same card type.
{% endhint %}


---

# 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/adding-a-card-to-a-cardholder.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.
