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

# Allegion Engage Interface

### Introduction

The Allegion Engage Interface is a licensed feature of Gallagher Command Centre. This feature supports the following Schlage wireless locks offered by Allegion:

* LE and LE-B locks
* NDE and NDE-B locks
* Control locks

**Notes:**

* Engage readers do NOT support Gallagher Mobile Credentials.
* While Engage Gateways, Doors and Card Types are all created in the Command Centre Configuration Client, Engage Scheduling is configured in Command Centre Client. See *"Allegion Engage Interface"* in the Command Centre Client Help file for further detail.
* A maximum of 8 Engage Gateways are supported per controller.
* A maximum of 80 locks are supported by a Controller.
* A maximum 10 locks are supported by an Engage Gateway.
* The Engage Gateway cannot be pinged as it will not handshake.

Gallagher encoded cards are not supported with this integration, you will need to use a Schlage encoded card. You can add a Gallagher DESFire object to the Schlage DESFire card to use these cards for both ENGAGE door locks and Gallagher readers. For further information see [Encoding Gallagher Credentials to an Engage Card](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/allegion-engage-interface/command-centre-configuration/encoding-gallagher-credentials-to-an-engage-card.md).

For further information about door/lock functionality, see [Engage Doors/Locks](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).

<details>

<summary>Process Overview to setup an Allegion Engage site</summary>

This topic is separated into several individual procedures that make up the process for setting up an Allegion Engage site. The procedures are performed in either Command Centre Configuration Client or the Allegion Engage™ Mobile App.

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

</details>

<details>

<summary>Engage Site architecture diagram</summary>

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

</details>

***

### Licensing

Allegion Engage is a licensable feature which requires one of the following license files with a unique license serial number for the Cloud:

| 2A08903 | Engage License with Hardware (per Door)    |
| ------- | ------------------------------------------ |
| 2A08904 | Engage License without Hardware (per Door) |

The License file must contain the following option:

`[Limits]`\
`ENGAGE Doors=X` (Where `X` is the number of Engage Doors required)

***

### Operator Privileges

The minimal operator privileges required for Engage are:

* "Launch Configuration Client"
* "Edit Site"
* "Configure Site" (for editing the Card Type)
* "Override"

***

Select the item below that you require further detail on:

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Creating an Engage Site in Gallagher Configuration Client](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/allegion-engage-interface/creating-an-engage-site-in-gallagher-configuration-client.md)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Allegion Engage configuration](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/allegion-engage-interface/allegion-engage-configuration.md)

![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f30c70c9dfd07493527af00bd979539606de5d30%2Ftopiclink.png?alt=media) [Command Centre configuration](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/allegion-engage-interface/command-centre-configuration.md)


---

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