> 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/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-configuration/lists/command-centre-lists/access-groups-list.md).

# Access Groups List

Creating an Access Group list is required if you plan to use access request workflows in AccessNow, for example, to enable users to request access to additional or secure areas. The Access Group list is imported from Command Centre. Each Command Centre Access Group in the list determines access to a selected area.

{% hint style="info" %}

## Command Centre Access Groups&#x20;

In Gallagher Command Centre, Access Groups are the primary mechanism for managing cardholder permissions by grouping individuals who share identical access criteria and operational privileges.

These groups define the three essential pillars of access control—who (the member cardholders), where (the permitted Access Zones), and when (the assigned Access Schedules)—while also establishing specific rights such as the ability to escort visitors or perform manual zone overrides.

Through a hierarchical concept called Lineage, child Access Groups automatically inherit the access requirements and privileges of their parent groups, and cardholders inherit any Personal Data Fields (PDFs) attached to their assigned groups.

Access Groups can be configured to grant memberships on either a permanent or temporary basis.
{% endhint %}

## Access Group List Management

Instructions for how to manage lists imported from the Command Centre follow the same for all of the list types including&#x20;

[Creating a New List ](/knowledge-hub/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-configuration/lists/command-centre-lists.md#creating-a-list-of-items-imported-from-command-centre)

[Renaming an Item](/knowledge-hub/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-configuration/lists/command-centre-lists.md#creating-a-list-of-items-imported-from-command-centre)

[Hiding an Items on a List ](/knowledge-hub/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-configuration/lists/command-centre-lists.md#hiding-a-list-item-in-accessnow)

[Synchronising a List with the Command Centre ](/knowledge-hub/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-configuration/lists/command-centre-lists.md#synchronising-lists-with-command-centre)

[Assigning Approvers to an Access Group](/knowledge-hub/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-configuration/lists/command-centre-lists/access-groups-list/assigning-approvers-to-access-groups.md)

[Removing Approvers from an Access Group](/knowledge-hub/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-configuration/lists/command-centre-lists/access-groups-list/removing-approver-groups-from-access-groups.md)


---

# 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/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-configuration/lists/command-centre-lists/access-groups-list.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.
