> 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/products/integrations/elevators/schindler/configure-schindler-id-data-synchronization.md).

# Configure Schindler ID data synchronization

Set up Schindler ID cardholder synchronization, Badge Number sources, and required Command Centre items.

Configure Schindler ID when Schindler needs Command Centre cardholder data. It supports Call by ID and Schindler terminals.

### Before you start

* Obtain the Badge Number format from the Schindler Technician
* Obtain the hexadecimal Badge Number string for third-party cards
* Assign each cardholder to an access group with User Template and Master Group personal data fields

### Create the Schindler ID system item

1. In Command Centre, go to **Configure > External System**.
2. Create a **SchindlerID System** item.

### Configure the credential source

Select one Badge Number source for each applicable card type.

| Source              | Value                            | Notes                                        |
| ------------------- | -------------------------------- | -------------------------------------------- |
| Card Type Specified | Facility Code and Card Number    | Available from Command Centre 7.30.          |
| MIFARE CSN          | Card Serial Number               | Supports four-byte and seven-byte CSNs.      |
| Direct PDF          | Manual Personal Data Field value | Command Centre does not validate this value. |

### Configure card types and credentials

1. In Command Centre, go to **Configure > Card Type**.
2. Create the card type or Mobile Credential item.
3. Configure the Schindler ID settings for the selected Badge Number source.

Gallagher-encoded DESFire cards require a SAM card with the MIFARE Site Key. Supported badge types are `None [0]` and `MIFARE DESFire [23]`.

### Create the Personal Data Field

1. In Command Centre, go to **Configure > Personal Data Field**.
2. Create a field with the **Elevator Car HLI** type.

### Confirm synchronization

Schindler ID sends cardholder changes one way to Schindler. Each card appears as a separate Schindler cardholder.

Cardholders require both the User Template and Master Group personal data fields. Without them, Schindler ID does not synchronize the cardholder.


---

# 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/products/integrations/elevators/schindler/configure-schindler-id-data-synchronization.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.