> 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/configuring-gallagher-command-centre-to-receive-source-data.md).

# Configuring Gallagher Command Centre to receive source data

### Introduction

Before you begin configuring an interface, you will need to ensure fields in Gallagher Command Centre have been created and configured to receive the source data.

When importing cardholder data into Command Centre, you may need to create the following Command Centre fields:

* Personal Data Fields
* Access Groups
* Cards
* Competencies, or
* Roles

When importing bookings into Command Centre, you will need to create the appropriate bookable resources. Refer to *Creating a Bookable Resource Item* (in the "Bookable Resources" feature release note).

Remote items in a multi-server environment can be mapped to Enterprise Data Interface. For ease of management, all items in a multi-server site should have a unique name to prevent confusion as to which card type, access group or competency is involved.

**Note:** When importing a cardholder's personal data, the data will be imported but may not show until the cardholder is added to the Access Group containing the Personal Data Field.

### Examples

* If you are importing a cardholder's license plate number.

  Ensure a 'License Plate' Personal Data Field has been configured in Gallagher Command Centre.
* If you are importing a cardholder's access privileges.

  Ensure an Access Group has been configured in Gallagher Command Centre that enables the cardholder to access the appropriate areas while on-site.
* If you are importing a booking. Ensure a bookable resource has been configured in Command Centre.


---

# 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/configuring-gallagher-command-centre-to-receive-source-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.
