> 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/administration/access-groups/creating-a-new-access-group.md).

# Creating a new Access Group

Perform the following procedure to create a new Access Group:

1. Click the **New Access Group** button on the Viewer Navigation Panel.

   The new Access Group is added to the Viewer Navigation Panel, and the Access Group Configuration pop-up displays.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-80b1ff260097a772c2ae9f87bc50f253eb310cf9%2Fagconfig_popup.png?alt=media)
2. If you want to replace the default name the system has given the Access Group, enter a new name in the **Name** field (limited to 60 characters).
3. If required, enter a logical **Description** (limited to 200 characters).
4. 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 Access Group 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 Access Group at a later stage.
5. If this Access Group is part of a hierarchy, select the "Immediate Parent" Access Group as follows:

   **Note:** See [Access Groups and Lineage](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/access-groups/access-groups-and-lineage.md) for an explanation of how hierarchy works.

   1. Select the **Parent** button (this appears as **-- None Selected --** by default).

      A browse tool displays.

      ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-3a3b486980d2ef2f6a42739e2a0d5d1bc7b54c2a%2Fselectparentag_popup.png?alt=media)
   2. Select the "Immediate Parent" Access Group from the browse tool.
   3. Click the **OK** button.

      The pop-up closes. The button changes to the name of the Access Group you selected and the Access Group moves to the appropriate position in the list in the Viewer Navigation Panel.

      All privileges assigned to the parent will be inherited by this Access Group.
6. Click the **Close** button.

   The Access Group Configuration pop-up closes, displaying the five configuration tabs.

   The **Access** tab displays by default.

   Click each tab in turn and configure the Access Group properties as required:

   * [Access tab](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/access-groups/creating-a-new-access-group/access-tab.md)
   * [Cardholders tab](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/access-groups/creating-a-new-access-group/cardholders-tab.md)
   * [Alarm Zone tab](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/access-groups/creating-a-new-access-group/alarm-zone-tab.md)
   * [History/Notes tab](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/generic-administration-tasks/history-notes-tab.md)
7. Click the **Save** button.

   A new Access Group has been created, and cardholders belonging to this Access Group can gain access to the specified zones at the specified times.

### Hints

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

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 Access Groups.
{% endhint %}

{% hint style="info" %}
**Duplicating Access Groups**

Operators privileged to create Access Groups can also duplicate Access Groups, which makes the task of setting up multiple Access Groups 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/administration/access-groups/creating-a-new-access-group.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.
