> 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-a-schindler-access-group.md).

# Configuring a Schindler Access Group

Create a Schindler Access Group. Refer to the topic Setting up Access Groups. Name the Access Group 'Schindler Access Group'.

Assign to this Access Group:

* Cardholders (Cardholders that require access to Schindler readers, terminals and lifts).
* The Schindler Access Zone previously configured. Cardholders belonging to this Access Group will inherit access to the Schindler Access Zone.
* The Schindler Cardholder Access Schedule previously configured (for the Schindler Access Zone).
* Schindler Personal Data Fields. Cardholders belonging to this Access Group will inherit the Schindler Personal Data Fields.

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

**Notes:**

* If a Cardholder is removed from the Schindler Access Group (thus the Cardholder no longer has the Schindler PDFs assigned), then an update will occur and the Cardholder will be removed from the Schindler user database.
* The Cardholder's last name must not be left empty, as this is a mandatory field in Schindler. If the Cardholder's last name is empty, the corresponding Schindler user will be deleted.
* If a Cardholder is removed from an Access Group that does not have the Schindler PDFs assigned, then an update will not occur.
* If a Cardholder has been assigned to a Temporary Access Group that has the Schindler PDFs assigned, then the Cardholder will be removed from the Schindler user database, once the temporary access has expired.


---

# 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-a-schindler-access-group.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.
