> 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/allegion-engage-configuration/commissioning-engage-doors-from-the-allegion-engage-mobile-app/engage-doors-locks.md).

# Engage Doors/Locks

If a new lock is introduced with a higher version of firmware, it is recommended to downgrade the lock to the same version as the existing gateway/locks, using the mobile app, before bringing the lock online.

**Note:** Engage Doors will not be included in Access Reports.

### Setting the time on the doors

As the Engage series make the decision to grant or deny access, they will be kept up to date with the time based on the time zone selected on the controller. If no time zone is selected, the doors will be updated with the server time. This solution does not support countries that have fixed daylight savings dates. In addition to this, countries that change daylight savings time between the hours of 4pm and 11pm, will have the time change take effect at 3pm. This can cause the access decisions made by the door to be out of sync with what is configured in Command Centre for a short period of time.

**Note:** The time on the door can creep. The door can be 2.5 minutes out from the gateway time, and the gateway will not force it to update. The gateway will check for the device time every 8 hours, and if it is more than 2.5 minutes out, it will push the gateway time down to the device. The controller time is also pushed to the gateway every day at 1am, and this is propagated to the doors. This creep shouldn’t be noticeable, but it can affect the time a cardholder will gain access.

### Door file

If there are changes to access schedules, access zones, or changes affecting all users, a full door file is required to be sent. Depending on the number of users on the doors, the changes can take up to 30.5 minutes to apply. While the change is in progress, the previous access configuration will still be in effect at the door. Here are some guidelines as to how long a full door file will take to apply:

* 200 Users, sync time is 94 sec (1.5 min)
* 300 Users, sync time is 118 sec (2.0 min)
* 2500 Users, sync time is 925 sec (15.5 min)
* 5000 Users, sync time is 1835 sec (30.5 min)

The following changes will trigger a full door file. Operators need to be aware of the implications of door access, (i.e. the old file will be in effect until the new one finishes downloading), which is dependent on the number of users on the door.

* Changing card type properties: Engage Card Type, UCF
* Hierarchy: Parenting or un-parenting an Access Group
* Access Group Field privilege: Entry allowed during lockdown
* Deleting Access Group
* Add/Modify/Remove Access Triplets (Engage Door, Engage Door Schedule, Engage Cardholder Access Schedule)

### Overrides

#### "Lockdown" and "Emergency Open"

When a "Lockdown" or "Emergency Open" override is cancelled, all doors will be placed in the state that the Schedule would have them in. This means if a door had been in 'privacy mode' prior to the override, after the override is lifted the door will no longer be in 'privacy mode'. Overrides also cancel privacy on doors.

#### "Door Open"

A "Door Open" override opens the door momentarily, and then it returns to the state it was in before it was unlocked.

**Notes:**

* Cardholders granted entry during "Lockdown" privilege will still adhere to the Engage Cardholder Access Schedule. This means if the door goes into lockdown and the schedule says to deny entry, they cannot get in. This differs from Gallagher behaviour.
* No overrides from the Access Zone will work for the Engage Doors.

### Control Lock

* The Control lock does not have a door sensor, so cannot be shown as open or closed. We can show if the state is in "lockdown" or "emergency open" mode, otherwise it will be shown as unknown.
* The Control lock cannot be put into a free state, including using the Engage Door Schedules, and overriding on the Engage Door.

### Low Battery

Installers will have between 3 and 4 weeks to replace a battery in a lock once a low battery alarm is raised. By the time the battery gets to the critical level, it will become inoperable.

### Card Activation and Expiry time for locks

For LE, LE-B, NDE and NDE-B locks, card activation and expiry time can only be set to the nearest hour. If a customer inputs minutes/seconds these will be ignored. This is a constraint of the device.

*For example:* If a card has an activation time of 1430, it will become active at 1400. If a card has an expiration time of 1430, it will expire at 1400.

### Multi-Server

Things that can be done in Multi-Server:

* Remote Engage Doors can be viewed from an Access Group
* Remote Access Groups can be viewed from the Engage Door Viewer and the Access Group
* Remote Access Groups can be added to a local Engage Door in the Door Viewer
* Local cardholders can gain access at remote Engage Doors

Things that **cannot** be done in Multi-Server:

* Remote Engage Doors cannot be viewed in the Engage Door Viewer
* Remote Engage Doors cannot be added to a local Access Group
* Overrides cannot be performed on Remote Engage Doors
* Remote Schedules cannot be viewed


---

# 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/allegion-engage-configuration/commissioning-engage-doors-from-the-allegion-engage-mobile-app/engage-doors-locks.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.
