> 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/schindler-event-reporting.md).

# Schindler Event Reporting

Select the appropriate Schindler reporting option.

* If the 'Report an error' option is selected, and a Cardholder has two cards assigned, then only one user will be imported into the Schindler 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. The event 'Card already assigned' is logged in Command Centre.
* If the 'Leave the card assigned to the existing user' option is selected and a Command Centre Cardholder has badge numbers assigned that match the badge numbers of an existing Schindler user, then the Command Centre Cardholder's badge numbers will not be imported. No event is logged in Command Centre.
* If the 'Assign the card to the new user' option is selected and a Command Centre Cardholder has badge numbers assigned that match the badge numbers of a Schindler user, then the badge numbers are removed from the Schindler user and assigned to the Command Centre Cardholder. No event is logged 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/site-installation/external-systems/schindlerid/schindler-event-reporting.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.
