> 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/allegion-engage-interface/command-centre-configuration/gallagher-command-centre-engage-door-configuration.md).

# Gallagher Command Centre Engage Door configuration

### Introduction

Access information is stored within the Engage Door itself. Credentials used to access the door are sent at card level, as opposed to the cardholder, and there is a limit of 5000 users allowed per door NDE and LE, and 500 per Control Lock.

This procedure details how to configure an Engage Door in Command Centre, once it has been created using the Allegion Engage™ Mobile App.

### Prerequisites

Doors must be created in the Allegion Engage™ Mobile App first (see [Commissioning Engage Doors from the Allegion Engage™ Mobile App](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/allegion-engage-interface/allegion-engage-configuration/commissioning-engage-doors-from-the-allegion-engage-mobile-app.md) for further detail), and then generated in Command Centre from the **Engage Doors** tab of the Engage Gateway (see [Gallagher Command Centre Engage Gateway configuration](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/allegion-engage-interface/command-centre-configuration/gallagher-command-centre-engage-gateway-configuration.md) for further detail).

### Configuration

To configure an Engage Door, perform the following procedure in Gallagher Configuration Client:

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

   The Engage List Window opens.
2. **Right click** on the Door to be configured, and select **Properties**.

   By default the **General** tab displays.

   **Note:** Engage Door names cannot be changed from Command Centre. They need to be changed in the Allegion Engage™ Mobile App, and then sent down to Command Centre.
3. Click the **Event Response** tab, and assign a primary Alarm Zone for all events.

   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).
4. Click the **Configuration** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-1d8ea6fa09e036c6ff388339d571853ab841cc34%2Fallegionengagedoor_configurationtab.png?alt=media)
5. The **Door Schedule**, **Access Template** and **Holiday Schedule** are assigned to the Door in Command Centre Client and cannot be altered here, (i.e. these fields are all 'read-only'). Refer to *"Allegion Engage Interface"* in the Command Centre Client Help file for further detail.
6. In the Permitted Card Technology section, **Use the server settings** is selected by default.

   If you want to select other types of cards to be accepted at the door, uncheck the **Use the server settings** checkbox and select the appropriate checkboxes.

   **Notes:**

   * Selecting **MIFARE Classic** or **125 kHz** technologies results in the following warning message:

     *"Some of the card technology options selected have known security vulnerabilities."*
   * The "Permitted Card Technology" section does not appear for Control locks.
7. Click the **Advanced** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-5c055f259191261b436b6bf32cc28f676212ef16%2Fallegionengagedoor_advancedtab.png?alt=media)
8. Configure the lock settings as required.

   <table><thead><tr><th width="157">Option</th><th>Description</th></tr></thead><tbody><tr><td>Battery Fail State</td><td><p>Select the required Door state from the drop-down list for when the battery runs out of charge:</p><ul><li>As is: Door will remain in the state configured before battery is discharged.</li><li>Free: Door will remain UNLOCKED when the battery is discharged.</li><li>Secure: Door will remain LOCKED when the battery is discharged.</li></ul><p>(Default = Secure)</p></td></tr><tr><td>Beeper Enabled</td><td>This is enabled by default meaning that the beepers of the door will be turned on. Unchecking this will turn the door’s beepers off.</td></tr></tbody></table>
9. Configure the Engage Door timeouts as required.

   <table><thead><tr><th width="157">Option</th><th>Description</th></tr></thead><tbody><tr><td>Door Unlock Time</td><td><p>This determines the maximum time the Unlock relay is energised.</p><p>(Valid range is 1 - 86400 seconds. Default = 5 seconds)</p></td></tr><tr><td>Extended Access Time</td><td><p>This setting determines an alternate unlock time, allowing the door to remain unlocked for longer than normal for those cardholders who require it, (e.g. disabled people, couriers, etc.).</p><p>(Valid range is 0 - 86400 seconds. Default = 25 seconds)</p><p>Refer to <a href="https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/doors/configuring-extended-access-time-for-a-door.md">Configuring alternate unlock time for a Door</a> for further details.</p></td></tr><tr><td>First Card Unlock</td><td>Normally if a schedule grants free access, even if no one has arrived, the door still goes to "Free-PIN". Enabling this setting stops the door from going to free until the first cardholder arrives and badges their card.</td></tr></tbody></table>
10. Click the **Icons** tab if you want to change the Icon Set for this Engage 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).
11. Click the **Custom Fields** tab if you want to add and assign a custom field value to this Engage 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).
12. Click the **Notes** tab if you want to add a note(s) about this Engage 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).
13. Click **OK** to exit and save your changes.

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

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

### Editing and Deleting Doors

Refer to [Editing items](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/editing-items.md) and [Deleting items](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/deleting-items.md) for procedures on how to edit and delete Engage Doors.

**Note:** If a door is deleted from Command Centre, it must also be removed from the site using the Allegion Engage™ Mobile App and factory reset before it can be re-used. Failure to factory reset the device can result in cardholders continuing to gain access to the door.


---

# 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/allegion-engage-interface/command-centre-configuration/gallagher-command-centre-engage-door-configuration.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.
