> 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/the-call-manager-interface-plugin/configuring-schindler-dummy-doors.md).

# Configuring Schindler Dummy Doors

### Introduction

A dummy Door is required for each terminal in the building.

**Note:** You do not need to create a dummy door for simulated terminals, used to control the secure/free state of floors.

***

### Configuration

To configure a Schindler dummy door, perform the following procedures in Gallagher Configuration Client:

1. Click **Configure** from the menu bar, then **Doors**.

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

   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 each tab in turn to configure a Schindler dummy door:

<details>

<summary>Event Response tab</summary>

1. Click the **Event Reponse** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-552ad88658e1e6eecf86a7bf8b1ca1aad305fb64%2Fschindler_terminaldummydoor.png?alt=media)
2. Select the **Card Event** Event Group and assign the Action Plan created for the terminal corresponding to this dummy door.
3. Select an **Alarm Zone** from the drop-down list that is common to all terminals in the Schindler system.

   **Note:** Doors must be placed into an Alarm Zone before you will receive Door Events.

</details>

<details>

<summary>Connections tab</summary>

1. Click the **Connections** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-b1188610bba48409a8ddd08a075247a452812805%2Fschindler_dummydoor_connectionstab.png?alt=media)
2. Assign the door to the Controller that will host this door.

   This should be the same Controller assigned to the External System Item representing each terminal.

</details>

<details>

<summary>Entry Zone tab</summary>

1. Click the **Entry Zone** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-d7fcfb0c1e7578017f7dd0206372d77b9ebd47de%2Fschindler_dummydoor2.png?alt=media)
2. Select an **Access Zone** from the drop-down list. Ensure the Schindler Access Zone Schedule (previously created) is assigned to the zone, and that Cardholder Access to this zone is 'Secure - No PIN' at all times.
3. From the **Reader(s)** drop-down list, select the appropriate reader that provides entry for this terminal.

</details>

5. Click the **Icons** tab if you want to change the Icon Set for this Door.

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

   For further details regarding the **Notes** tab, see [Notes](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/notes.md).
7. Click **OK** to exit and save your changes.
8. Repeat this procedure to configure a dummy door for each terminal in the building.


---

# 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/the-call-manager-interface-plugin/configuring-schindler-dummy-doors.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.
