> 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/integrated-systems/schlage-lock-interface/creating-a-schlage-door-in-command-centre.md).

# Creating a Schlage Door in Command Centre

### Introduction

This procedure describes how to create a Schlage Door in Gallagher Command Centre.

### Configuration

To configure a Schlage Door, perform the following procedures in Gallagher Configuration Client:

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

   The **Hardware** List Window opens (in [tree view](https://help.security.gallagher.com/knowledge-hub/configuration-client/glossary-of-terms.md#tree-view)).
2. **Right click** and select **New\...Schlage Devices** > **Schlage 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 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 the door:

<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-b0648656ebc81938cdfbf9a631a6eaa30189a30c%2Fschlagedoor_connections_tab.png?alt=media)

   The three fields, (i.e. **Connected to**, **RS-485 Bus** and **Device Number** ) will be populated once you assign this door to a Schlage PIM, which is explained later in [Assigning Devices](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/schlage-lock-interface/assigning-devices.md).

</details>

<details>

<summary>Configuration tab</summary>

1. Click the **Configuration** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-353dc9b0144046c58b2b3735de7c741e756821aa%2Fschlagedoor_configuration_tab.png?alt=media)
2. Select the appropriate entry and exit zones for this door from the **Entry Zone** and **Exit Zone** drop-down lists.

   **Note:** Exit Zones always show the puzzle icon if they are only assigned to Schlage Doors.
3. Click the **Door Mode** field and select the appropriate mode from the drop-down, (i.e. "Classroom/Storeroom", "Office" or "Apartment").

   **Important:** These door modes are supported on AD devices from v8.80. To make sure this feature works correctly:

   1. Update Command Centre to vEL8.80 or later.
   2. Update the Controller software to the latest version.
   3. Once all updates are complete, right-click on the AD Lock and click **Push Configuration**.
   4. Right-click on the Alarm Zone and click **Push Configuration**.

   <table><thead><tr><th width="184">Door Mode</th><th>Explanation</th></tr></thead><tbody><tr><td>Classroom/Storeroom</td><td><p>The door access is totally controlled by the Entry Access Zone. It works the same way as normal Gallagher doors. Pressing the IPB (Inside Push Button) indicates the door secure/free mode as follows:</p><ul><li>Red LED flash = door locked (secure)</li><li>Green LED flash = door unlocked (free)</li></ul><p>"Classroom/Storeroom" door mode is the default setting after door set up.</p></td></tr><tr><td>Office</td><td><p>Without the IPB (Inside Push Button) function, "Office" mode functions the same way as "Classroom/Storeroom" mode. Pressing the IPB button changes the lock status to the opposite state of the access zone schedule. Pressing the IPB button again brings the AD lock back to access zone schedule status.</p><p>Once the door goes back to access zone schedule status, the next IPB change will be counted as the 'First' IPB state change. During the IPB state time, if access zone schedule changes or /override/lockdown applied, will change the AD lock status.</p><p>The IPB button LED should show lock/unlock state of the door for each IPB pressing:</p><ul><li>1 green flash = in IPB state and door unlocked</li><li>1 red flash = in IPB state and door locked</li><li>2 green flashes = back to access zone and door unlocked</li><li>2 red flashes = back to access zone and door locked</li></ul></td></tr><tr><td>Apartment</td><td><p>The door does not follow an Access Zone Schedule. Its lock/unlock behaviour is controlled by the end user, i.e. pressing the IPB (Inside Push Button) or badging a valid card toggles the door access between lock and unlock. Pushing inside handle to request to exit puts the door to unlock.</p><p>"Apartment" door mode supports the Access Zone lockdown feature.</p><p><strong>Note:</strong> The door will not return to lockdown state automatically when the door is unlocked via the inside handle/IPB button, you will need to press the IPB button to re-secure the door.</p><p>There are other Access Zone features that are not supported in this mode, (e.g. Access Zone Schedule, Access Zone normal overrides, double card overrides, PIN, Dual Authorisation are not supported).</p><p>The Apartment mode LED patterns are:</p><p><strong>Inside IPB LED:</strong> Any door inside behaviours (press IPB button or press inside handle to exit) will cause the IPB LED flash, showing the result secure state:</p><ul><li>1 green flash = door unlocked (free)</li><li><p>1 red flash = door locked (secure)</p><p><strong>Outside Schlage LED:</strong> Badge card outside of the door will cause the Schlage LED flashing, showing result secure state and card valid or not:</p></li><li>1 red flash = badge valid card, and the door is changed to locked(secure) when door in closed.</li><li>2 green flashes = badge valid card, and the door is unlocked(free) or locked but door is open.</li><li>2 red flashes = badge invalid card.</li></ul></td></tr></tbody></table>
4. Select the appropriate checkboxes in the Permitted Card Technology section to indicate what types of cards will be accepted at the door.

   **Notes:**

   * Selecting **MIFARE Classic**, **125 kHz** or **Magstripe** technologies result in the following warning message:

     *"Some of the card technology options selected have known security vulnerabilities."*
   * For AD-400 and AD-402 devices, card technology and PIV authentication mode changes may need 1-2 door heart beat time to take effect.
5. Did you select the **PIV** checkbox?

   If **no**, go to the **Advanced** tab.\
   If **yes**, then an additional **PIV Settings** tab will display.

   **Note:** Only AD302 and AD402 locks can be configured to use PIV cards, and PIV support requires a Gallagher PIV Controller 6000 or 7000.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-150f61183e2575adfea1690a889fd2b488e8e923%2Fschlagedoor_pivsettings_tab.png?alt=media)
6. Select the appropriate Authentication Mode by clicking the relevant radio button.

   **Notes:**

   * Only one authentication mode can be selected.
   * PIV Authentication mode is only valid when using PIV Contactless cards.
   * For AD-400 and AD-402 devices, card technology and PIV authentication mode changes may need 1-2 door heartbeat time to take effect.
7. Go to the **Advanced** tab.

</details>

<details>

<summary>Advanced tab</summary>

1. Click the **Advanced** tab.

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

   The settings on this screen enable alarms to trigger.
2. Check the **PIN is user code** checkbox if required.

   With **PIN is user code** checked, the user code will be required in place of a PIN for any transactions at the reader which would normally require a PIN. This includes door access and overrides.

   **Notes:** The following settings do not work in **PIN is user code** mode:

   * *Double-card overrides*. Therefore, if you do select **PIN is user code** mode, leave the Double card overrides as **Disabled**.
   * *"Apartment" Door Mode*. If "Apartment" has been selected (on the **Configuration** tab) and you select **PIN is user code**, the following warning message will display:

     *"Schlage doors in the apartment mode do not support User code or PIN."*
3. If you want the double-card override feature to be available, click either the **Override access zone** or the **Arm alarm zone** radio button, depending on whether you want the double-card override to override the state of the Access Zone or arm the Alarm Zone associated with the Access Zone.

   **Notes:**

   * Access Group Privileges are required for the overrides to work.
   * If "Apartment" door mode has been selected (on the **Configuration** tab), and you select either of the **Double card overrides**, the following warning message will display:

     *"Schlage doors in the apartment mode do not support double card overrides."*
4. Configure the Schlage Door timeouts as required.

   <table><thead><tr><th width="211">Option</th><th>This setting determines...</th></tr></thead><tbody><tr><td>Door unlock time</td><td><p>the maximum time the Unlock relay is energised.</p><p>(Default = 5 seconds. Valid range is 1 - 255 seconds)</p></td></tr><tr><td>Card to complete action must be presented within</td><td><p>the maximum time between two card badges.</p><p>(Default = 5 seconds. Valid range is 1 - 99 seconds)</p></td></tr><tr><td>PIN (for PIN entry) failed if not entered correctly within</td><td><p>either:</p><ul><li>the maximum time between badging a card and starting to enter a PIN at the reader for access through a door in PINs mode, <strong>OR</strong></li><li>overriding an Access Zone or Alarm Zone in PINs mode.</li></ul><p>(Default = 10 seconds. Valid range is 1 - 99 seconds)</p></td></tr><tr><td>Door warns 'Open Too Long' if still open after</td><td><p>when the open warning output turns on and when the status of the door changes to show that it has been open too long.</p><p>(Default = 20 seconds. Valid range is 0 - 9999 seconds)</p><p><strong>Note:</strong> This cannot be set as greater than the alarm time, (i.e. the <strong>Door is 'Open Too Long' time</strong>). If it is, and you attempt to save the door, the following error message displays:</p><p><em>"The 'Open Too Long' warning time must be less than or equal to the 'Open Too Long' alarm time."</em></p></td></tr><tr><td>Open warning</td><td>the Output to activate when the door has been open too long.</td></tr><tr><td>Door is 'Open Too Long' if still open after</td><td><p>when a 'Door Open Too Long' alarm is generated.</p><p>(Default = 20 seconds. Valid range is 5 - 9999 seconds)</p></td></tr><tr><td>Door is 'Forced Open' if opened unexpectedly</td><td><p>whether an alarm will be generated. When checked, a 'Forced Door' alarm will be generated if the open sensor detects the door is opened.</p><p><strong>Note:</strong> Unchecking this will result in no 'Forced Door' alarms being generated, therefore it is recommended you leave it checked.</p></td></tr><tr><td>Extended access time</td><td><p>the maximum time the door is to unlock for.</p><p>(Default = 25 seconds. Valid range is 0 - 255 seconds)</p><p><strong>Note:</strong> The <strong>Extended access time</strong> affects the times used for all of the following:</p><ul><li>Door unlock time</li><li>Door Open Too Long Warning</li><li>Door Open Too Long Alarm</li></ul></td></tr></tbody></table>

</details>

7. Click the **Cameras** tab if you want to associate a DVR Camera(s) with this Schlage Door.

   For further details see [Cameras tab](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/cameras-tab.md).
8. Click the **Icons** tab if you want to change the Icon Set for this Schlage 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).
9. Click the **Custom Fields** tab if you want to add and assign a custom field value to this Schlage Door.

   For further details regarding the **Custom Fields** tab, see [Custom Fields](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/custom-fields.md).
10. Click the **Notes** tab if you want to add a note(s) about this Schlage 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).
11. 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/integrated-systems/schlage-lock-interface/creating-a-schlage-door-in-command-centre.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.
