> 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/site-installation/external-systems/schindlerid/cardholder-management-interface/configuring-schindler-cardholders.md).

# Configuring Schindler Cardholders

Create the Cardholders that require access to Schindler readers, terminals, and lifts. Configure the Schindler Personal Data Field values for each Cardholder. Assign each Cardholder at least one card; Cardholders without a card are not synchronised.

To map the Schindler Personal Data Field values, refer to the following topics:

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Mapping the Schindler User Template](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/external-systems/schindlerid/cardholder-management-interface/configuring-schindler-cardholders/mapping-the-schindler-user-template.md)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Mapping the Schindler Parent Group](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/external-systems/schindlerid/cardholder-management-interface/configuring-schindler-cardholders/mapping-the-schindler-parent-group.md)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Mapping Schindler Badge Numbers](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/external-systems/schindlerid/cardholder-management-interface/configuring-schindler-cardholders/mapping-schindler-badge-numbers.md)

**Notes:**

* The Schindler 'User Template' and 'Parent Group' PDFs must be assigned to each Cardholder, otherwise the Cardholders are **not** imported into the Schindler user database.
* At least one card must also be assigned to each Cardholder, otherwise the Cardholders are **not** imported into the Schindler user database.
* If a Cardholder has the Schindler 'User Template' and 'Parent Group' PDFs assigned and has **two cards or more** assigned, then the Cardholder is imported as two or more users into the Schindler user database.
* If a Cardholder has the Schindler 'User Template', 'Parent Group' and 'Badge Number' PDFs assigned and two cards assigned, then only one user will be imported into the Schindler user database. This user will have the badge numbers assigned. The second user will not be imported because the badge numbers are already assigned to the first user.
* If a Cardholder does not have the PDF Badge Numbers assigned, when an update occurs, Badge Numbers already configured for this user in the Schindler user database will be removed. To avoid this, assign the PDF Badge Numbers to the Cardholder and type ' **ignore** ' as the data value for the first badge number and leave the other two badge numbers empty.

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-df5e1267cc2fa2a93cfe3a73c10f0b86a135f20a%2Fschindler_3.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/site-installation/external-systems/schindlerid/cardholder-management-interface/configuring-schindler-cardholders.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.
