> 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/command-centre-client/configuring-command-centre/configuring-licensable-features/allegion-engage-interface.md).

# Allegion Engage Interface

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

**Note:** While Engage scheduling is configured in the Command Centre Client, Engage Gateways, Doors and Card Type are all created in the Configuration Client. Therefore, see *"Allegion Engage Interface"* in the Configuration Client Help file for further detail.

### Licensing

Allegion Engage is a licensable feature, therefore the functionality will only appear if your site has a license file with a unique license serial number for the Cloud, and the following option included:

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

### Operator Privileges

The minimal operator privileges required for Allegion 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:

[Engage Schedules](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/configuring-licensable-features/allegion-engage-interface/engage-schedules.md)

[Creating a new Engage Door Schedule](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/configuring-licensable-features/allegion-engage-interface/creating-a-new-engage-door-schedule.md)

[Creating a new Engage Holiday Schedule](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/configuring-licensable-features/allegion-engage-interface/creating-a-new-engage-holiday-schedule.md)

[Creating a new Engage Cardholder Access Template](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/configuring-licensable-features/allegion-engage-interface/creating-a-new-engage-cardholder-access-template.md)

[Creating a new Engage Cardholder Access Schedule](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/configuring-licensable-features/allegion-engage-interface/creating-a-new-engage-cardholder-access-schedule.md)

[Engage Doors](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/configuring-licensable-features/allegion-engage-interface/engage-doors.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/command-centre-client/configuring-command-centre/configuring-licensable-features/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.
