> 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/cardholder-interface-configuration-example.md).

# Cardholder Interface configuration example

### Introduction

The following is a fictional example, showing how a source file containing student details will be imported into Gallagher Command Centre.

### Example

The following table shows how source fields have been mapped to Gallagher Command Centre fields.

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

#### Access Group Memberships

Course codes will be used to define a student's Access Groups,

(i.e. the areas a student can access while on-site).

The following table shows the course codes present in the source file and what Access Groups they will be mapped to.

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

If a student has a Carpark Membership value, the student will be placed in the Carpark Access Group, (i.e. the student will have access to the carpark).

The Carpark Start and Finish dates will be used to define the period of access the student has to the carpark.

#### Cards

The Card Type value will be used to define a student's card type. The Start and Finish dates will be used to define the card's enablement period.

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


---

# 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/cardholder-interface-configuration-example.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.
