> 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-call-by-profile.md).

# Configure Schindler Call by Profile

Configure Call by Profile with REST access, Middleware plugins, and Schindler profile mappings.

Configure Call by Profile to send a Schindler profile name after access approval. This method does not synchronize cardholder data to Schindler.

### Before you start

* Choose Call by Profile instead of Call by ID
* Create the Personal Data Field that stores each Schindler profile name
* Ensure the REST operator can view cardholders and their changes

### Configure the Middleware

1. Install the Call Manager Interface Plugin on the Middleware PC.
2. Install the Life/Live Reporting Plugin when Command Centre needs Schindler events.
3. Enable Call by Profile in the Middleware configuration.
4. Set the profile Personal Data Field name in the Middleware configuration.
5. Configure the REST API URL, API key, and client certificate thumbprint.

The Middleware caches profiles retrieved through the REST API. Configure a default profile for cardholders without an assigned profile.

### Configure the external system item

1. Configure the External System Item for the Schindler terminal.
2. Set its **Triggered Output** to `[CN]_[FC]_[CI]_[BT]`.
3. Configure an Action Plan to trigger the item.

The fields identify the credential and cardholder. The Middleware uses `[CI]` to retrieve the cardholder profile through REST.

### Assign Schindler profiles

1. Enter a profile name in the configured Personal Data Field.
2. Match the name exactly to a profile configured in Schindler.

Schindler denies access when the names differ.

### Confirm licensing

Enable the `SchindlerHLICallbyProfile`, `RESTCardholders`, and `RESTEvents` features. Enable the Schindler ID Life Reporting and Call Interface plugins.

### Confirm the access flow

1. Present a credential at the Gallagher reader.
2. Confirm Command Centre approves the access request.
3. Confirm the Middleware sends the profile name to Schindler.

Use the Middleware log when the output does not contain all four fields.


---

# 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-call-by-profile.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.