> 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/enterprise-data-interface/configuring-an-interface/mapping-cardholder-data.md).

# Mapping cardholder data to Gallagher Command Centre fields

### Introduction

This section of the manual describes how to map cardholder data from your source data to Gallagher Command Centre fields.

Before you can begin mapping you will need to decide the purpose of your cardholder interface. To either:

* Add or update cardholders, or
* Remove cardholders

There is one ID field used to identify the cardholder in Gallagher Command Centre, (e.g. Student ID or Employee ID). Refer to [Creating a cardholder ID mapping](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/enterprise-data-interface/configuring-an-interface/mapping-cardholder-data/creating-a-cardholder-id-mapping.md).

### Adding or updating cardholders

If the purpose of your interface is to add or update cardholders, complete the following procedure:

**Note:** When adding cardholders, you must create a map to the Division field.

1. Click the **Mappings and Operator** tab.
2. Click **Configure**.

   This tab displays the fields you defined on the Data Format tab (these fields originate from your source data) and all Gallagher Command Centre fields that can have data imported.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-77043426dd6ee3ad03f3dc16aaefe9663bcc0ef0%2Fmapping.png?alt=media)
3. Select **Add or update** from the Cardholder mode drop-down list.
4. If you want to retain the cardholder's pre-existing Access Groups, select **Merge** from the Access Group mode drop-down list.
5. If you want to set Access Groups to the mapped Access Groups only, select **Replace** from the Access Group mode drop-down list.
6. To continue mapping source fields to Gallagher Command Centre fields, refer to the following topics:
   * [Creating a cardholder ID mapping](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/enterprise-data-interface/configuring-an-interface/mapping-cardholder-data/creating-a-cardholder-id-mapping.md)
   * [Creating a cardholder direct mapping](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/enterprise-data-interface/configuring-an-interface/mapping-cardholder-data/creating-a-cardholder-direct-mapping.md)
   * [Creating a cardholder transformation mapping](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/enterprise-data-interface/configuring-an-interface/mapping-cardholder-data/creating-a-cardholder-transformation-mapping.md)

### Removing cardholders

If the purpose of your interface is to remove cardholders, complete the following procedure:

1. Click the **Mappings and Operator** tab.
2. Click **Configure**. The Edit Mappings window opens.
3. Select **Remove** from the Cardholder mode drop-down list.
4. Create an ID mapping. Refer to [Creating a cardholder ID mapping](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/enterprise-data-interface/configuring-an-interface/mapping-cardholder-data/creating-a-cardholder-id-mapping.md). Cardholders whose unique Personal Data Field value matches the unique source value will be removed. Other mappings can exist, but they will have no effect when removing cardholders.


---

# 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/enterprise-data-interface/configuring-an-interface/mapping-cardholder-data.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.
