> 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-schindlerid-system.md).

# Configuring a SchindlerID System

### Introduction

This topic describes how to create a SchindlerID System. The SchindlerID System interfaces with the Schindler Third Party Database Interface.

**Notes:**

* Operators require the "Edit Site" operator privilege to be able to add, modify, and delete SchindlerID Systems.
* The total number of SchindlerID Systems you can create is determined by your licence file.

***

### Before you begin

Create the Schindler Third Party Database in Schindler.

Request Schindler integrators to create a Schindler Third Party Database, and provide the following database information:

* The Schindler server name or IP Address of the computer used to create the Schindler Third Party Database.
* The TCP/IP Port Number of the Schindler Third Party Database.

***

### Configuration

To configure a SchindlerID System, perform the following procedures in Gallagher Configuration Client:

1. Click **Configure** from the menu bar, then **External Systems**.

   The **External Systems** List Window opens (in [tree view](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/tree-view.md)).
2. **Right click** and select **New\...SchindlerID System**.

   By default the **General** tab displays.
3. Complete the fields as required.

   For further detail see [General tab](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/general-tab.md).
4. Click the **Event Response** tab, and configure as required.

   For further detail see [Event Response tab](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/event-response-tab.md).
5. Click the **Alarm Instructions** tab, and configure as required.

   For further detail see [Alarm Instructions tab](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/alarm-instructions-tab.md).
6. Click each tab in turn to configure a SchindlerID System:

<details>

<summary>SchindlerID Setup tab</summary>

1. Click the **SchindlerID Setup** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f743580ac84ea9ff0177d1932134deebda166ec6%2Fschindler_system1.png?alt=media)
2. Enter the Schindler server PC’s IP Address in the **Server PC Name/IP Address** field. This field is limited to 255 alpha-numeric characters.
3. Enter the TCP/IP Port Number of the Schindler Third Party Database Interface in the **Port** field. This value is located in the Schindler Third Party Database Interface. Valid range 1 – 65535.
4. Select the **Mask Cardholder Names** checkbox to hide Cardholders' names within this Schindler system (e.g. to ensure Cardholder privacy). Since Cardholders require a first and last name in the Schindler system, selecting this checkbox replaces Cardholder names in the Schindler system rather than removing them. If this checkbox is checked, each Cardholder entry in the Schindler system has both the first and last names replaced by the Cardholder's card number and facility code, in the format \[card number]\_\[facility code].

   This checkbox does not hide or change any Cardholder names within Command Centre. If you select this checkbox, all existing Cardholder names in the Schindler system are masked. Likewise, if you deselect this checkbox, all existing Cardholder entries in the Schindler system are updated with their real names.
5. If required, select a Card Type or Mobile Credential from the **Card Type** drop-down list. If selected, only Cardholders configured with this Card Type or Mobile Credential will be imported into the Schindler user database. If left as '-- None Selected --', all Cardholders that have any Card Type card or Mobile Credential will be imported into the Schindler user database.

</details>

<details>

<summary>Personal Data Fields tab</summary>

1. Click the **Personal Data Fields** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-a7ecf6ad727ae5cf7bbc51de3337ba484a2178b8%2Fschindler_pdfs.png?alt=media)
2. Select the PDF that corresponds to the Schindler **User Template** field.
3. Select the PDF that corresponds to the Schindler **Master Group** field.
4. Select the PDF that corresponds to the Schindler **Department** field, (optional).
5. Select the PDFs that correspond to each of the Schindler **Badge Number** fields, (optional).

   **Note:** If using Schindler readers the Badge Number PDFs are required.

</details>

<details>

<summary>Advanced tab</summary>

1. Click the **Advanced** tab.

   **Note:** If you selected a Mobile Credential type for the Card Type on the **SchindlerID Setup** tab, the **Advanced** tab is not applicable. Only configure this tab if you selected a ‘Card Type’ type.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-b82503f5f4f439c49204a9692ceca684a99285a2%2Fschindler_advanced.png?alt=media)
2. Select the appropriate **Badge Number Preference** for each Badge Number.

   Badge Number options are:

   * **Direct PDF**

     This option will use the Badge Number PDF (previously selected) as the Badge Number field in Schindler
   * **MIFARE CSN**

     This option will use the Cardholder's MIFARE CSN as the Badge Number field in Schindler. This option is allowed for one Badge Number field only. This option supports 4-byte and 7-byte CSN only.

     Cardholder cards may need to be (re)captured in Command Centre in order to store each card's CSN in the Command Centre database. A Cardholder's CSN can be captured by presenting the card to a USB MIFARE Encoder in a Cards tile in the Command Centre Client, or in the Configuration Client -> Monitor -> Read MIFARE Card.

     **Important:** If a Badge Type of **-- None Selected --** has been configured in the SchindlerID System, it assumes that the Badge Type **MIFARE \[1]** is configured in Schindler, otherwise the Badge Type configured in the SchindlerID System must correspond to the Badge Type configured in Schindler.

     Command Centre will construct the hexadecimal string using the card's MIFARE CSN and prepend the string with the leading zeros to extend the string length to the configured Badge Number Length.

     For example: 000000000A436AC1 (16 hexadecimal digits).

     The relevant Badge Number field can be verified in Schindler as:
   * **Card Type Specified**

     If this option is selected, the Badge Number hexadecimal number string will be constructed according to the specification of the **Badge Number Format** configured for the relevant Card Type. This option is allowed for one Badge Number field only.

   **Note:** After a 'Badge Number Preference' is changed on a SchindlerID System item, an automatic resync of the item is performed in order to update the Cardholders' relevant Badge Number field.
3. To specify the Badge Number Length, enter the required length in the **Badge Number Length** field. Zeros will be prepended to the hexadecimal string to extend the string length to this number of characters. Default = 16.
4. If the 'Card Type Specified' option has been specified as a Badge Number Preference, select the required Schindler **Badge Type** from the **Badge Type** drop-down list.

   **Important:** The Badge Type configured here must correspond to the Badge Type configured in Schindler.

   <table><thead><tr><th width="192">Option</th><th>Description</th></tr></thead><tbody><tr><td>-- None Selected --</td><td>This is the default and is backward compatible with the existing 'Mifare CSN' Badge Number Preference option.<br>This option only supports 4-byte MIFARE CSN when the 'Mifare CSN' Badge Number Preference has been selected.</td></tr><tr><td>None [0]</td><td>For supporting multiple Badge Types. Each Badge Number hexadecimal number string in the update message must explicitly specify a two-digit Badge Type at the start.<br>If 'Mifare CSN' is selected as a Badge Number field, this option supports both 4-byte and 7-byte CSN.</td></tr><tr><td>MIFARE [1]</td><td>Only for 4-byte CSN.</td></tr><tr><td>InterISO14443A [21]</td><td>Only for 7-byte CSN.</td></tr><tr><td>Pure Wiegand [37]</td><td>For Wiegand formats with parity bits.</td></tr><tr><td>MIFARE DESFire [23]</td><td>Supports MIFARE® DESFire® card data including Gallagher encoded card data.</td></tr></tbody></table>

</details>

7. Click the **Icons** tab if you want to change the Icon Set for this SchindlerID System.

   For further details regarding the **Icons** tab, see [Icons](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/icons.md).
8. Click the **Notes** tab if you want to add a note(s) about this SchindlerID System.

   For further details regarding the **Notes** tab, see [Notes](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/notes.md).
9. Click **OK** to exit and save your changes.

   Click **Cancel** to exit without saving your changes.

   Click **Apply** to save your changes and stay in this window.


---

# 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-schindlerid-system.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.
