> 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/creating-a-cardholder-direct-mapping.md).

# Creating a cardholder direct mapping

### Introduction

This procedure describes how to create a cardholder direct mapping.

A direct mapping imports the exact wording from your source field into Gallagher Command Centre. You can create direct mappings for the following Gallagher Command Centre fields:

* Cardholder fields
* Personal Data fields (including notification PDFs)
* Access Groups
* Cards
* Competencies
* Relationships

You can import (map) data from a single source field to more than one Gallagher Command Centre field.

**Notes:**

* If a blank or null value is mapped to the Authorised field, new cardholders will be Authorised. For existing cardholders, this value will remain unchanged.
* If regular expression validation is configured on the PDF field being mapped to, then Enterprise Data Interface will also validate data as it is imported to make sure that it matches the configured regular expression.
* When mapping from a database, if the source field is a related data field containing multiple values and the destination field can only accept a single value, then the cardholder record will not be imported.
* If the source field contains a blank or null value, refer to [Mapping blank values](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/enterprise-data-interface/configuring-an-interface/mapping-cardholder-data/mapping-blank-values.md).

### Procedure

1. Select the ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-30489e4dc6cdafeae78b7842dc608d1a686e89aa%2Fstraightbutton.gif?alt=media) tool.
2. Select the source field you wish to map from.
3. Hold down the mouse button and drag the cursor over the Gallagher Command Centre field you wish to map to.
4. Release the mouse button. A black line appears between the two fields and a message appears in the window below.

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

   For direct mappings to fields such as Notification PDF fields, Access Groups, Cards, Competencies and Relationships, additional information may be supplied as part of the mapping. This information is shown in the panel below the mappings.

   For relationship mappings, a role and a related cardholder ID field must also be selected for the mapping to be valid.

   **Notes:**

   * When adding cardholders, you will need to create a map to the Division field.
   * If the source field contains a blank value, refer to [Mapping blank values](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/enterprise-data-interface/configuring-an-interface/mapping-cardholder-data/mapping-blank-values.md).
   * If a blank value is mapped to the Authorised field, new cardholders will be Authorised. For existing cardholders, this value will remain unchanged.
   * If regular expression validation is configured on the PDF field being mapped to, then Enterprise Data Interface will also validate data as it is imported to make sure that it matches the configured regular expression.


---

# 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/creating-a-cardholder-direct-mapping.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.
