> 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/licensable-features/visitor-management/command-centre-site-configuration/assigning-permanent-cardholders-to-cardholder-division.md).

# Assigning permanent cardholders to Cardholder Division

### Introduction

This procedure describes how to assign permanent cardholders to the **Cardholder Division**, allowing them to be potential visitors, (e.g. visiting a site within the same organisation).

**Note:** The bulk changes feature can be used if you want to change the division for a large number of cardholders. Refer to [Initiating a new Cardholder Bulk Change](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/bulk-changes/initiating-a-new-cardholder-bulk-change.md) for the procedure.

### Procedure

1. Click **Manage** from the menu bar.
2. Click **Cardholders**.

   The **Cardholder** List Window opens.
3. **Right click** on the Cardholder you want to assign to the Cardholder Division, and select **Properties**.

   By default the **General** tab displays.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-6ff07fc7ab566bdddb9536ea7d1f27cd74328aad%2Fchold_generaltab.png?alt=media)
4. Select the "Cardholder Division" from the **Division** drop-down list.
5. Click the **OK** button.
6. Repeat Steps 3 to 5 for every cardholder you want to assign to the Cardholder Division.


---

# 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/licensable-features/visitor-management/command-centre-site-configuration/assigning-permanent-cardholders-to-cardholder-division.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.
