> 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/configuration-client/integrated-systems/salto-lock-interface/command-centre-site-configuration/configuring-access-groups.md).

# Configuring Access Groups

### Introduction

A Salto Access Triplet is the relationship between an Access Group, a Salto Access Zone or Salto Door, and a Schedule. These appear as rows on the Salto Access tab of an Access Group.

This procedure describes how to configure an Access Group in Command Centre to accommodate a Salto Access Triplet.

### Procedure

1. Click **Manage** from the menu bar, then **Access Groups**.

   The **Access Group** List Window opens (in [tree view](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/tree-view.md)).
2. **Right click** and select **New\...Access Group**.
3. Configure the new Access Group as required.

   See [Setting up Access Groups](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/access-groups/setting-up-access-groups.md) for further detail.
4. Click the **Salto Access** tab.

   **Note:** This tab is only available if your site is licensed for one or more Salto Doors.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-52eec5d8697e53fd0c8bd3eb65aa1059426b0b65%2Faccessgroup.png?alt=media)
5. Click **Configure** from the menu bar, then **Salto**.

   The **Salto** List Window opens.
6. Select those Salto Access Zone(s), Salto Door(s), Salto ESD(s), Salto Room(s), Salto Suite(s), or Salto Locker(s) appropriate for this Access Group.

   Drag and drop them into the **Salto Access** tab.

   **Notes:**

   * It is recommended that you assign Salto Access Zones to the Access Group, rather than a large number of Doors. This will help minimise the data required on a Cardholder's card.
   * The Salto Access Zone may already contain the appropriate Salto devices for this Access Group. If this is the case, you will only need to assign the Salto Access Zone to this Access Group.
   * Salto Access Zones cannot be mixed with Command Centre Access Zones for viewing.
7. Close the **Salto** List Window.
8. Click **Configure** from the menu bar, then **Schedules**.

   The **Schedule** List Window opens.
9. Select the Cardholder Access Schedules appropriate for this Access Group.

   Drag and drop them into the **Salto Access** tab.
10. Close the **Schedule** List Window.
11. Click **OK** to exit and save your changes.

    Click **Cancel** to exit without saving your changes.

    Click **Apply** to save your changes and stay in this window.


---

# 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/configuration-client/integrated-systems/salto-lock-interface/command-centre-site-configuration/configuring-access-groups.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.
