> 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-new-cardholder.md).

# Adding a New Cardholder

### Introduction

Details for every person requiring access to Command Centre sites must be set up within Command Centre.

This procedure is split into two parts, as follows:

* Creating Cardholders,

  (i.e. providing the minimum information required to create a new Cardholder)
* Configuring a Cardholder,

  (i.e. linking the various components to it - Card Types, Access Groups, Operator Groups and Personal Data Fields are the components of a Cardholder).

You can create a new Cardholder, then configure it at a later stage, once you have set up the necessary components for it.

**Note:**

Your site license will determine the number of Cardholders you can have, therefore once you have added all you are allowed, the option to create more will be disabled.

***

### Configuration

#### Create the Cardholder

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. **Right click** and select **New\...Cardholder**.

   By default the **General** tab displays.
3. Complete the fields as required.

   For further detail see [General tab](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/general-tab.md).
4. Click the **Apply** button, and the Cardholder is created. The rest of this procedure allows you to fully configure the Cardholder.

#### Configure the Cardholder

5. Ensure the following information has already been set up:

   *Divisions*

   Refer to "[Setting up System Division](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/system-division/setting-up-system-divisions.md)".

   *Card Types*

   Refer to "[Setting up Card Types](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/card-types/setting-up-card-types.md)".

   *Access Groups*

   Refer to "[Setting up Access Groups](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/access-groups/setting-up-access-groups.md)".

   *Operator Groups*

   Refer to "[Setting up Operator Groups](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/operator-groups/setting-up-operator-groups.md)".

   *Personal Data Fields*

   Refer to "[Creating a new Personal Data Field](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/personal-data-fields/creating-a-new-personal-data-field.md)".
6. Click each tab in turn to configure a new Cardholder:

<details>

<summary>Cards tab</summary>

Click the **Cards** tab.

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

This tab allows you to add cards to a Cardholder. See [Adding a card to a Cardholder](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/cardholders/adding-a-card-to-a-cardholder.md) for procedure.

</details>

<details>

<summary>Access Groups tab</summary>

1. Click the **Access Groups** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-0bf74f6bd21ac1a1ce1924a6b37cd396f23869a7%2Fchold_accessgroupstab.png?alt=media)
2. Click **Manage** from the menu bar, then **Access Groups**.

   The **Access Group** List Window opens.

   Select the Access Group(s) that the cardholder will belong to.

   Drag and drop them into the **Access Groups** tab.

   **Notes:**

   * It is recommended that you do not assign a cardholder to any more than ten Access Groups, as too many Access Groups per cardholder will result in slow access responses. See [Setting up Access Groups](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/access-groups/setting-up-access-groups.md) for further detail.
   * A cardholder can be granted temporary access to an Access Group. See [Temporary Access](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/access-groups/temporary-access.md) for further details.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-7406eb247c4877a28406c8b52b69bef9a47541b6%2Fagintoch.png?alt=media)
3. Close the **Access Group** List Window.

</details>

<details>

<summary>Personal Data tab</summary>

Click the **Personal Data** tab.

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

See [Editing a Cardholders PDF data](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/cardholders/editing-a-cardholders-pdf-data.md) for the procedure.

</details>

<details>

<summary>Notes tab</summary>

Click the **Notes** tab if you want to add a note(s) about this cardholder.

**Note:** Depending on your operator privileges, the **Notes** tab may or may not display.

For further details regarding the **Notes** tab, see [Notes](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/notes.md).

</details>

<details>

<summary>User Code tab</summary>

Configuration on this tab is only required if your site has HBUS Terminals installed, and this cardholder will be required to access these Terminals.

1. Click the **User Code** tab.

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

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-9df0b4836e1d5fbfeedd6f23f8c27cca009da894%2Fnewchold_code.png?alt=media)
2. Enter a 4-8 digit User Code that will be used to identify this cardholder at a HBUS Terminal.

   **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.

</details>

<details>

<summary>Operator Configuration tab</summary>

Configuration on this tab is only required if this Cardholder is an Operator.

**Note:** The Operator Configuration tab only displays if you have "Edit Cardholders" and "Edit Operators" privileges.

1. Click the **Operator Configuration** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-6ad51b87a99538a26cec22c8a60ae435ae3b0815%2Fchold_opconfigtab.png?alt=media)
2. See [Configuring Operators](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/operator-groups/configuring-operators.md) for the procedure.

</details>

7. 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.

### Result

A new cardholder is added.

***

### Editing and Deleting Cardholders

Refer to [Editing items](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/editing-items.md) and [Deleting items](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/deleting-items.md) for procedures on how to edit and delete Cardholders.

**Note:** Although deleted, a Cardholder's actions may still appear in an Activity Report. Refer to [Activity Report](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/reports/creating-a-new-report/activity-report.md).

***

### Hints

{% hint style="info" %}
**Copy and paste**

An alternative to the drag and drop method is to use the copy and paste method.
{% endhint %}

{% hint style="info" %}
**Copying cardholder details**

To speed up the process of adding new cardholders, details for the new Cardholder can be copied from an existing cardholder. See [Copying Cardholder details](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/cardholders/copying-cardholder-details.md).
{% endhint %}

{% hint style="info" %}
**Operator Configuration details**

When a system administrator sets up a cardholder as an operator in Command Centre, they will provide the operator with a Logon Name and Password. When the operator logs on to Command Centre for the first time they need to change their password. See [Changing Operator Passwords](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/getting-started/operator-passwords/changing-operator-passwords.md).
{% endhint %}

{% hint style="info" %}
**Advanced drag and drop feature**

Cardholders can be dragged and dropped directly from their own List Window into another List Window. See [Using the advanced drag and drop feature](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/getting-started/using-the-advanced-drag-and-drop-feature.md) for further detail.
{% 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-new-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.
