> 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-cardholder-access-template.md).

# Creating a new Engage Cardholder Access Template

Creating an Engage Cardholder Access Template provides you with an item that you can add entries to, which will be used to create schedules that can control access. (Limited to 16 entries.)

**Note:** There is a Default Cardholder Access Template that can be modified to suit. The Default Cardholder Access Template is automatically assigned to doors at door creation, so modifying the default to cater for the majority of access requirements can save time in changing the template out on the door.

Perform the followinf procedure to create a new Engage Cardholder Access Template:

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 Cardholder Access Template** option.

   The new Engage Cardholder Access Template 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-502d9026fa26a7d7de117ca6b446b082eaf4698d%2Fengagecardholderaccesstemplateconfigurationpopup.png?alt=media)
3. If you want to replace the default name the system has given the Engage Cardholder Access Template, 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 Engage Cardholder Access Template 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. **Schedules** and **History/Notes** ). The **Schedules** tab displays by default.

   The **Access Granted Periods** section provides a grid where different access times can be entered/edited during the 24-hour cycle for each day of the week. Initially the grid will be blank.

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

   **Note:** The **Assigned Items** section shows a list of Cardholder Access Schedules and Doors that the template is attached to.
7. Click the **Add Access Granted Period** button.

   The Access Granted Period pop-up displays.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-cd6f3a4a673598057f1dd5fd4195c81734a9e5f9%2Faccessgrantedperiod_popup.png?alt=media)
8. Alter **From** and **Until** time boxes to indicate the period you want access to be granted for.
9. Check each of the day(s) as required that you want access to be granted for.
10. Click the **OK** button.

    The Access Granted Period pop-up closes/
11. Repeat Steps 7-10 to add more Access Granted Periods to the Template.
12. If you you want to record any note(s) about the Template, 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.
13. Click the **Save** button.

    A new Engage Cardholder Access Template has been created.

**Note:** After the template has been assigned to a schedule/door and you select an entry, the list of Engage Cardholder Access Schedules will change depending on whether they use the entry or not.


---

# 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-cardholder-access-template.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.
