> 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-doors/configuring-access-groups-with-engage-schedules.md).

# Configuring Access Groups with Engage Schedules

### Prerequisites

Before you begin this procedure, you need to have created the Engage Doors, Engage Cardholder Access Schedules, and the Access Groups you will be configuring.

### Procedure

Perform the following procedure to configure where members of this Access Group have access to (Engage Doors) and when they have access (Schedules):

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

   The Access Groups Viewer opens.
2. Click on the Access Group you want to configure Engage Schedules for from the list in Viewer Navigation Panel.

   The properties for that Access Group populate the Viewer Panel.
3. Click the **Engage Doors** tab.

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

   The **Engage Doors** section allows you to set where members of this Access Group have access to (Engage Doors) and when they have access (Schedules).
4. Click the **Add Engage Access** button.

   The Add Engage Door / Schedule Pairs pop-up displays.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-2e06331d0b8ef5b84630d4721acafc229ea31d75%2Fselectengagedoor_step1.png?alt=media)
5. If necessary, search for the Cardholder Access Schedule you want by entering characters in the **Search** field and/or refining the search mode and filters. The grid becomes populated with Cardholder Access Schedules that match the search criteria.
6. Click the radio button next to the Schedule you want to use, then click the **Select Schedule** button.

   The Add Engage Door / Schedule Pairs pop-up changes to show a list of available Engage Doors to select from.

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

   **Note:** The list will only include Engage Doors that can use the selected schedule (via the Engage Cardholder Access Template).
7. Click the checkbox next to each Engage Door you want to include and click the **Add Selection** button.

   Alternatively, click the **Select All** button if you want to include all Doors.

   The pop-up closes and the selected Engage Door(s) and Cardholder Access Schedule populates the **Engage Doors** section.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-475dcf697185110c71947555381104aa23d56ff8%2Faccessgroups_engagedoorstab_populated.png?alt=media)
8. Check the **Entry During Lockdown and Privacy Mode** checkbox in the **Access Privileges** panel to allow Cardholders in the Access Group to gain entry to the Engage Doors when the doors have been put into lockdown state by an operator, or privacy mode by physically pushing the pushbutton.

   **Notes:**

   * The cardholder access schedule will still apply, (i.e. if the Engage Cardholder Access Schedule does not allow access at the time, the cardholder will not gain access regardless of the doors state, e.g. locked, lockdown, privacy).
   * Enabling **Entry During Lockdown and Privacy Mode** applies to Engage Doors only. If the cardholders in the Access Group need this privilege for other doors, this needs to be selected on the **Access** tab.
9. Click the **Show Inherited Access** button to see whether or not the Access Group has inherited the lockdown privilege from a parent group.
10. Click the **Save** button.

    The Access Group Assignment is saved.

    **Notes:**

    * If you decide to change the Engage Cardholder Access Schedule you have selected, click on the Schedule in the **Engage Doors** section and select another one from the browse tool that displays.

      ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-32199d91c63b2b3db31f2d975919793d606212b3%2Fchangeecaschedule_fromag.png?alt=media)
    * To remove an Access Group Assignment, select (highlight) the row you want to remove and click the **Remove** button. Multiple actions can be selected for removal by holding down the < **Ctrl** > key while each action is clicked on, and then clicking the **Remove** button.


---

# 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-doors/configuring-access-groups-with-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.
