> 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/site-management/access-groups/setting-up-access-groups.md).

# Setting up Access Groups

### Introduction

This procedure is split into two parts, as follows:

* Creating an Access Group,

  (i.e. providing the minimum information required to create a new Access Group)
* Configuring an Access Group,

  (i.e. linking the various components to it - Divisions, Cardholders, Schedules, Access Zones and Personal Data Fields are the components of an Access Group).

You can create a new Access Group, then configure it at a later stage, once you have set up the necessary components for it.

***

### Configuration

#### Create the Access Group

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**.

   By default the **General** tab displays.
3. Complete the fields as required.

   For further detail see [General tab](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/general-tab.md).
4. Click the **Apply** button, and the Access Group is created.

   The rest of this procedure allows you to fully configure the Access Group.

#### Configure the Access Group

5. Ensure the following information has already been set up:

   *Divisions*

   Refer to "[Setting up System Division](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/system-division/setting-up-system-divisions.md)".

   *Cardholders*

   Refer to "[Add New Cardholder](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/cardholders/adding-a-new-cardholder.md)".

   *Schedules*

   Access Schedules = relating to cardholders

   Access Zone Schedules = relating to how the doors within the zone behave

   Refer to "[Schedule](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/schedules.md)".

   *Access zones*

   Includes a linked Access Zone Schedule

   Refer to "[Adding a new Access Zone](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/access-zones/adding-a-new-access-zone.md)".

   *Personal Data Fields*

   Refer to "[Creating a new Personal Data Field](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/personal-data-fields/creating-a-new-personal-data-field.md)".

   *Notifications*

   Refer to "[Creating a Notification Filter](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/notifications/creating-a-notification-filter.md)".
6. Click each tab in turn to configure the Access Group:

<details>

<summary>Lineage tab</summary>

1. Click the **Lineage** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-a86b80e7f39db67c2e2937aeaed7c6de007d423a%2Faglineage.png?alt=media)
2. If this Access Group is part of a hierarchy, select the "Immediate Parent" access group from the drop-down list.

   All privileges assigned to the parent will be inherited by this Access Group.

</details>

<details>

<summary>Cardholder Membership tab</summary>

1. Click the **Cardholder Membership** tab.
2. Click **Manage** from the menu bar, then **Cardholders**.

   The **Cardholder** List Window opens.
3. Select those Cardholders to belong to the new Access Group.

   Drag and drop them into the **Cardholder Membership** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-fbd2bd336c98853570831fa37263030101d65c5b%2Fchintogroup.png?alt=media)
4. Close the **Cardholder** List Window.
5. Cardholders that have no 'From' and 'Until' dates beside their names are permanent members of the Access Group.

   If you want to make any Cardholders temporary members, (i.e. give them access for a limited period of time), see [Granting Temporary Access by Access Group](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/access-groups/temporary-access/granting-temporary-access-by-access-group.md) for the procedure.

</details>

<details>

<summary>Membership Defaults tab</summary>

1. Click the **Membership Defaults** tab.

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

   This screen allows a membership period to be set up for the Access Group.

   By default, the start and end dates are set to none, therefore membership is permanent. See [Granting Temporary Access by Access Group](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/access-groups/temporary-access/granting-temporary-access-by-access-group.md) for further detail.

</details>

<details>

<summary>Access tab</summary>

1. Click the **Access** tab.
2. Click **Configure** from the menu bar, then **Access Zones**.

   The **Access Zone** List Window opens.

   Select those zones appropriate for this Access Group.

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

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-807733f35e38db1fa53b9390aeadb2f78258735d%2Fazintogroup.png?alt=media)

   **Note:** There is a limit of 255 Alarm Zones/Access Zones per Access Group per Controller. If this limit is exceeded, an alarm will be generated (in the Alarm Viewer window), and the first 255 zones only will be sent to the Controller.
3. Close the **Access Zone** List Window.
4. Click **Configure** from the menu bar, then **Schedules**.

   The **Schedule** List Window opens.
5. Select those Access Schedules appropriate for this Access Group.

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

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-cb2b84088539907d43472719b9081ac5e5518ba8%2Fasintogroup.png?alt=media)
6. Close the **Schedule** List Window.

</details>

<details>

<summary>Privileges tab</summary>

1. Click the **Privileges** tab.

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

   Cardholder Privileges are configured in Access Groups.

   When you add Cardholders to an Access Group they automatically inherit the privileges as configured for that Access Group. (For a more detailed explanation see [Inheritance of Access Group Privileges](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/access-groups/access-groups-and-lineage.md).)
2. Select the appropriate **Access Privileges** as required for the Access Group.

   <table><thead><tr><th width="198">Access Privilege</th><th>Enables members to...</th></tr></thead><tbody><tr><td>Visitor</td><td>be escorted through selected Access Zones by someone with 'Escort' privileges for the same Access Zones.</td></tr><tr><td>Escort visitors</td><td>escort visitors to the Access Zones (according to the schedules) assigned to the Access Group.</td></tr><tr><td>Lock and unlock access zones</td><td>change the state of an Access Zone that the Access Group gives access to, from a card reader. This is known as a 'local override'. For further details refer to <a href="https://help.security.gallagher.com/knowledge-hub/configuration-client/site-monitoring/status-and-overrides/configuring-local-overrides-at-card-readers.md">Configuring Local Overrides at Card Readers</a>.</td></tr><tr><td>Entry allowed during lockdown</td><td>enter Access Zones contained in the Access Group when those Access Zones are in lockdown mode, provided they meet the access criteria required during lockdown. When a site is placed in lockdown mode, certain people, (e.g. emergency services) will still require entry. For further details refer to <a href="https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/access-zones/access-zone-lockdown/performing-a-lockdown-override.md">Performing a Lockdown Override</a>.</td></tr><tr><td>First Card Unlock</td><td>unlock an Access Zone from SECURE state to FREE state, once access is granted.</td></tr></tbody></table>

   **Note:** When a site is licensed for Aperio Doors, there will be two additional access privileges, as follows:

   <table><thead><tr><th width="198">Access Privilege</th><th>Enables members to...</th></tr></thead><tbody><tr><td>Aperio Privacy Override</td><td><p>unlock doors even when in Privacy Mode. Default = unticked.<br><br><strong>Notes:</strong></p><ul><li>Privacy Mode is activated by a button on certain Aperio locks. This feature needs to be enabled in Aperio Programming Application Protocol (PAP) in order to take effect.</li><li>An Aperio door that is closed, locked, and in Privacy Mode displays a red and yellow padlock icon in the <strong>Hardware</strong> window of Configuration Client.</li></ul></td></tr><tr><td>Aperio Offline Access</td><td>unlock doors even when the door is offline (only supported by V3 type locks; V2 type locks do not support this functionality).<br><strong>Important:</strong> This feature is considered a potential security risk and should be used sparingly.<br><br><strong>Note:</strong> This feature requires configuration in PAP to turn the mini cache on and determine how long the cache entries live for (maximum 30 days). The cache can be cleared at any time from Command Centre.</td></tr></tbody></table>
3. Select the **Alarm Zone Privileges** required for this Access Group.

   <table><thead><tr><th width="196">Alarm Zone Privilege</th><th>Enables members to...</th></tr></thead><tbody><tr><td>Change to the Disarmed state</td><td>disarm Alarm Zones associated with any Access Zone associated with the Access Group.</td></tr><tr><td>Change to the Armed state</td><td>arm Alarm Zones associated with any Access Zone associated with the Access Group</td></tr><tr><td>Change fence HV/LF mode</td><td>change the HV/LF mode of an Alarm Zone associated with any Access Zone associated with the Access Group.</td></tr></tbody></table>

   **Note:**

   The **Terminal Privileges** section of this tab relates only to HBUS Terminals or HBUS Alarms Only Terminals. Therefore, these privileges should only be selected if your site is using one of these terminals and this Access Group will be using them.

   Refer to [Configuring Access Group Privileges for Terminal Access](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/access-groups/configuring-access-group-privileges-for-terminal-access.md) for further detail.

</details>

<details>

<summary>Terminal Access tab</summary>

1. Click the **Terminal Access** tab.

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

   The Cardholder Access Schedule selected here, determines when the members of this Access Group can log on to an HBUS Terminal or HBUS Alarms Only Terminal.

   The **Terminal Access** tab can be used to configure periodic testing, to allow members of this Access Group to disarm the system via a Terminal.

   If this functionality is required, refer to [Configuring Access Groups for Test Modes](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-monitoring/alarm-input-test-modes/configuring-access-groups-for-test-modes.md) for further detail.

</details>

<details>

<summary>Alarm Zones tab</summary>

1. Click the **Alarm Zones** tab.
2. Click **Configure** from the menu bar, then **Alarm Zones**.

   The **Alarm Zone** List Window opens.

   Select those Alarm Zones appropriate for this Access Group.

   Drag and drop them into the Alarm Zones tab window.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-2449f8b85166ad9a93e3181a021ab0747c06fcb8%2Faztab.png?alt=media)
3. Close the **Alarm Zone** List Window.

</details>

<details>

<summary>Personal Data tab</summary>

1. Click the **Personal Data** tab.
2. Click **Configure** from the menu bar, then **Personal Data Fields**.

   The **Personal Data Field** List Window opens.

   Select those Personal Data Fields appropriate for this Access Group.

   Drag and drop them into the Personal Data tab window.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-401fe20261ea6a6e40c6b4cf7ae61f01772ce65f%2Fagpdf.png?alt=media)
3. Close the **Personal Data Field** list Window.

</details>

<details>

<summary>Anti-Passback Response tab</summary>

1. Click the **Anti-Passback Response** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-915e66eacfd54d4036c030b28b0ac648d44ef1cb%2Fag_antipassresptab.png?alt=media)

   This tab allows you to configure the responses you require for Anti-Passback violations and Anti-Tailgating violations.

   <table><thead><tr><th width="192">Term</th><th>Definition</th></tr></thead><tbody><tr><td>Anti-Passback violation</td><td>A condition where the system has detected that a card passback has occurred, (i.e. a cardholder has attempted to enter an Access Zone, or Access Zone Group, when they are already recorded as within it).</td></tr><tr><td>Anti-Tailgating violation</td><td>A condition where the system has detected that a cardholder has tailgated, (i.e. a cardholder has attempted to enter an Access Zone when they are currently recorded as outside the Access Zone, or Access Zone Group, from which they are entering).<br><br><strong>Note:</strong> While the anti-tailgating response is configured here on the Access Group, the "Check for tailgating on exit from zone" option is configured on the Access Zone.</td></tr></tbody></table>
2. Click the appropriate radio buttons for the responses you require.

</details>

7. Click the **Custom Fields** tab if you want to add and assign a custom field value to this Access Group.

   For further details regarding the **Custom Fields** tab, see [Custom Fields](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/custom-fields.md).
8. Click the **Notes** tab if you want to add a note(s) about this Access Group.

   For further details regarding the **Notes** tab, see [Notes](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/notes.md).
9. 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.

### Result

Cardholders belonging to the Access Group can gain access to the specified zones at the specified times.

**Note:** This new Access Group defaults into the "Immediate Children" box on the Lineage tab of the Access Group you selected as the "Immediate Parent".

***

### Editing and Deleting Access Groups

Refer to [Editing items](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/editing-items.md) and [Deleting items](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/deleting-items.md) for procedures on how to edit and delete Access Groups.

***

### Hints

{% hint style="info" %}
**Find tool**

Dragging individual items (for example Access Zones) can be laborious. Using the Find tool you can speed up the procedure:

* Open the Find window.
* Set up the appropriate search criteria.
* Within the Search list window, select a continuous range or the required separate items.
* Drag the items into the appropriate Access Group window.
  {% endhint %}

{% hint style="info" %}
**Copy and paste**

An alternative to the drag and drop method is to use the copy and paste method.
{% endhint %}

{% hint style="info" %}
**Personal Data details**

The Personal Data Field(s) you added to this Access Group (on the **Personal Data** tab) will now have this Access Group displayed in the **Group Membership** tab of their Properties screen.
{% 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/configuration-client/site-management/access-groups/setting-up-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.
