> 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/quick-tips-for-working-with-engage-doors.md).

# Quick Tips for working with Engage Doors

* Engage Doors get created in the Allegion Engage™ Mobile App, and are then generated in Command Centre from the **Engage Doors** tab of the Engage Gateway.
* 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.
* The Navigation Panel on the left-hand side displays all the Engage Doors. Engage Doors with unsaved changes will be in **bold** and have a **\*** at the end of their name.

### Configuration tab

* Engage Doors are restricted by the number of Schedules they can contain. This tab allows Engage Schedules to be configured for the Engage Door.

### More information

For more information, refer to the topic *"Allegion Engage Interface"* in the Gallagher Command Centre Online Help.


---

# 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/quick-tips-for-working-with-engage-doors.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.
