> 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-installation/setting-up-your-site/wizards/configuration-wizard/creating-cardholders.md).

# Creating Cardholders

### Introduction

The **Cardholder Wizard** allows you to create cards and cardholders. Operators require the "Edit Cardholder", "Modify Access Control" and "View Site" operator privileges (all in the correct division) to run the Cardholder Wizard.

### Cardholder Wizard

The **CardholderWizard** contains a number of pages which prompt you to enter certain information to create Cardholders.

**Follow the instructions displayed.**

### Procedure

1. Click the **Cardholders** radio button.
2. Select the type of card you want to create from the **Card Type** drop-down list.
3. Click the **Start** button.

#### 'Cards' page

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

4. Configure the details as appropriate.
5. Click the **Next** button.

   The final screen of the **Cardholder Wizard** displays.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-0df4296b88b03136548dca4f4bd47b493aa6a83f%2Fchwizard_scrn2.png?alt=media)
6. Click the **Finish** button.

   Once the Progress bar reaches the end, the Configuration Wizard launch page re-displays.

**Note:**

The **Cardholder** wizard allows you to create cards and cardholders. You define a range of card numbers to add to the system (with a limit of 1000 cards at a time), and as a result the Cardholder list window is populated with the same amount of cardholders as cards created, (e.g. if you created a range of card numbers from 1 to 300, there would be 300 new cardholders displayed).

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

The cardholders appear with the word "Card" as the **First Name** and the card number as the **Last Name**. Now when you replace these with actual cardholders names, the process is a lot quicker as they have already got card numbers assigned to them, and they are assigned to an Access Group.

The cardholders are configured as shown below, (i.e. they have Issue Level 1. the cardholders are authorised, they have no expiry date and the 'Resident' and 'Card Trace' options are not set).

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

If you enter card numbers that already exist, cardholders are only created for the numbers up to the first one that already exists, and then no more are created. An error message will display when the first existing card is found, and card creation stops.

**Examples:**

* Cards 1 to 10 already exist. An operator tries to create cards 5 to 50.

  None are created.
* Cards 1 to 10 and 20 to 40 already exist. An operator tries to create cards 11 to 70.

  Only cards 11 to 19 are created.


---

# 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-installation/setting-up-your-site/wizards/configuration-wizard/creating-cardholders.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.
