> 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/creating-a-new-engage-door-schedule.md).

# Creating a new Engage Door Schedule

The Engage Door Schedule allows you to set the times that Engage Doors will be free and secure on normal days, while not exceeding the limit of 16 entries in the door. Perform the following procedure to create a new Engage Door Schedule:

**Notes:**

* There is a Default Door Schedule that can be modified to suit. The Default Door Schedule is automatically assigned to doors at door creation, so modifying the default to cater for the majority of free/secure requirements can save time in changing the template out on the door.
* Door schedules are not followed by doors in Apartment Mode.

1. Select the **Administration** tab on the Command Centre title bar, and then click the **Schedules** button on the toolbar.

   The Schedules Viewer opens.
2. Click the **New Schedule** button on the Viewer Navigation Panel, and then the **Engage Door Schedule** option.

   The new Engage Door Schedule is added to the Viewer Navigation Panel, and the Schedule Configuration pop-up displays.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-fb90ad25a87376bc568b791bc10a66ec86a244ea%2Fengagedoorscheduleconfigurationpopup.png?alt=media)
3. If you want to replace the default name the system has given the Schedule item, enter a new name in the **Name** field (limited to 60 characters).
4. If required, enter a logical **Description** (limited to 200 characters).
5. The **Division** button defaults to the name of the last Division in which the Operator created a Command Centre item, regardless of whether it was created in Configuration Client or via Command Centre Client.

   If this is not the appropriate Division for this Schedule to be in, select a Division as follows:

   1. Click the **Division** button.

      A browse tool displays.

      ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-5ea28b89c753564de542b1b9c1b328d1e0fc8c60%2Fselectdivisionforviewer_popup.png?alt=media)
   2. Select the appropriate Division.
   3. Click the **OK** button.

      The pop-up closes and the button changes to the name of the Division you selected.

   **Note:** If you have not set up Divisions yet, you can add these to your Schedule at a later stage.
6. Click the **Close** button.

   The Schedule Configuration pop-up closes.

   There are two tabs, (i.e. **Schedule Entries** and **History/Notes** ). The **Schedule Entries** tab displays by default.

   The **Schedule Times** section provides a grid where 'From' times and states can be entered/edited for each day of the week. Initially the default state of 'Secure' will display.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-360cdbd629c37fd72d8e059bdcb287df90b4b41a%2Fengagedoorschedule_scheduleentriestab.png?alt=media)

   **Note:** The **Scheduled Doors** section shows a list of Doors that the schedule is attached to.
7. Click the **Manage State Changes** button.

   The Add State Changes pop-up displays.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-887159e841065af312efb618f5d025f6ac283e94%2Fengagedoorschedule_addstatechangespopup.png?alt=media)
8. Click the **Add State Change** button.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-67adc1c0da1ab7110b74641ca8b09f113166da13%2Fengagedoorschedule_addstatechangespopup2.png?alt=media)
9. Check each day(s) as required that you want to change the state for.
10. Select the appropriate **State** from the drop-down list.
11. Alter the **From** Time Box to the time you want that State to change from.

    The State/time bar for the day(s) selected changes accordingly.

    ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-627aefd4bfec66abd769b1ab86ffb5e9aa716cbe%2Fengagedoorschedule_addstatechangespopup3.png?alt=media)
12. Repeat Steps 8-11 for any other state changes you want to make.
13. Click the **OK** button.

    The Add State Changes pop-up closes.
14. If you you want to record any note(s) about the Schedule, click the **History/Notes** tab.

    Refer to [History/Notes tab](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/generic-administration-tasks/history-notes-tab.md) for further detail.
15. Click the **Save** button.

    A new Engage Door Schedule has been created.

### Hints

{% hint style="info" %}
**Editing and Deleting Schedules**

Refer to [Editing items](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/generic-administration-tasks/editing-items.md) and [Deleting items](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/generic-administration-tasks/deleting-items.md) for procedures on how to edit and delete Schedules.

**Note:** If a schedule has items which depend upon it for proper operation, you are prompted for confirmation and cannot delete it even when **Yes** is clicked. A message explaining why you cannot delete the schedule displays.
{% endhint %}

{% hint style="info" %}
**Duplicating Schedules**

Operators privileged to create schedules can also duplicate schedules, which makes the task of setting up multiple schedules that are very similar much quicker.

Refer to [Copying items](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/generic-administration-tasks/copying-items.md) for the procedure.
{% endhint %}


---

# 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/creating-a-new-engage-door-schedule.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.
