> 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/engage-schedules.md).

# Engage Schedules

Engage Doors are restricted by the number of Schedules they can contain. Each lock has three Schedule types, as follows:

<table><thead><tr><th width="166">Schedule type</th><th>Description</th></tr></thead><tbody><tr><td>Engage Cardholder Access Template and Schedule</td><td>The Engage Cardholder Access template is assigned directly to the door, and this template is the 'schedule' the door uses. A single entry can manage multiple days, (e.g. one entry can be used for all weekdays). These are assigned to users of the lock and dictate when access will be granted or denied to the cardholder. If there are different types of cardholders, (e.g. staff, cleaners), the access schedules for all cardholder types must not exceed 16 in total.<br><br><strong>Note:</strong> Only "access granted" types will be counted as an entry.<br>The Engage Cardholder Access Schedule is known as the <em>Credential Schedule</em> by the Engage lock, and references different entries in the template. They are part of the access triplet, whereas the template is assigned directly to the door. In Command Centre, once the template has been created the user can select the entries from the template when creating the schedule.</td></tr><tr><td>Engage Door Schedule</td><td>This schedule is known as the <em>Auto-Unlock Schedule</em> by the Engage lock and determines when the door will be free or secure. (Limited to 16 entries.)<br>Each change to free and secure will count as an entry. Like the Credential Schedule, a single entry can manage multiple days.</td></tr><tr><td>Engage Holiday Schedule</td><td>This schedule is known as the <em>Holiday Schedule</em> by the Engage lock and is like the <em>Auto-Unlock Schedule</em> in the sense that the operator can select free and secure states. (Limited to 16 entries per day.) When a day falls on a date set in the Holiday Schedule, the free and secure times will be determined by the Holiday Schedule, as opposed to the <em>Auto-Unlock Schedule</em>.<br>The cardholders will be granted or denied access as per the credential schedule.</td></tr></tbody></table>


---

# 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/engage-schedules.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.
