> 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/configuring-access-group-privileges-for-terminal-access.md).

# Configuring Access Group Privileges for Terminal Access

### Introduction

This procedure describes how to assign [*Alarm Zones*](https://help.security.gallagher.com/knowledge-hub/configuration-client/glossary-of-terms.md#alarm-zone) to an Access Group and specify associated privileges for HBUS Terminal and HBUS Alarms Only Terminal use.

Operators require the “Edit Access Group” operator privilege, and must be in the same or parent Division of the Access Group and the Alarm Zones.

***

### Configuration

To configure Access Group Privileges for Terminal access, perform the following procedures in Gallagher Configuration Client:

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. Highlight the Access Group you wish to assign Alarm Zones to and **double-click** the mouse button.
3. Click each tab in turn to configure the Access Group privileges:

<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-2fff37dba1fe63d8b0a1ef9b81d1aedfa745fcd5%2Fagforrat.png?alt=media)
2. The **Access Privileges** and **Alarm Zones Privileges** have probably already been configured when this Access Group was created.

   Change if necessary.
3. In the **Terminal Privileges** section of this tab, select the appropriate privileges as required for the Access Group.

   <table><thead><tr><th width="223">Privilege</th><th>HBUS Terminals</th></tr></thead><tbody><tr><td>View alarms and items</td><td>This privilege enables a user to view all available alarms and items on an HBUS Terminal or HBUS Alarms Only Terminal.</td></tr><tr><td>Shunt items</td><td>This privilege enables a user to shunt and unshunt items using an HBUS Terminal or HBUS Alarms Only Terminal.</td></tr><tr><td>Acknowledge all alarms</td><td>This privilege enables a user to acknowledge all available alarms using an HBUS Terminal or HBUS Alarms Only Terminal.</td></tr><tr><td>Acknowledge alarms below high priority</td><td>This privilege enables a user to acknowledge all available alarms below high priority using an HBUS Terminal or HBUS Alarms Only Terminal.</td></tr><tr><td>Lock out fence zones</td><td>This privilege enables a user to lockout selected Fence Zones using an HBUS Terminal or HBUS Alarms Only Terminal.<br>The fence cannot be energized when in lockout mode. Lockout is persisted during a Fence Controller or Controller restart (it is not persisted during a DIP Switch 2 Controller restart).<br>Only the user that placed the fence into lockout mode can remove lockout mode (unless the "Cancel others lockout" privilege has been assigned to another user). Lockout mode can only be removed using the HBUS Terminal or HBUS Alarms Only Terminal that was used to put the fence into lockout.</td></tr><tr><td>Cancel others lock out</td><td>This privilege enables a user to cancel the lockout of selected Fence Zones initiated by another user.<br>This is only possible from the HBUS Terminal or HBUS Alarms Only Terminal that was used to put the fence into lockout.</td></tr><tr><td>Prompt for alarm zone selection</td><td>This privilege enables a user to view a list of Alarm Zones for which the user’s Access Group assignment provides privilege for, from the <strong>Menu</strong> screen on an HBUS Terminal or HBUS Alarms Only Terminal.</td></tr><tr><td>Force-arm alarm zones with any alarms</td><td><p>If an Alarm Zone would not normally arm because there were any potential, unacknowledged or active alarms, by having this privilege and either the "Override" or "Override up to Medium Priority" operator privilege, a user will be provided with the option to force-arm the Alarm Zone, when arming from an HBUS Terminal or HBUS Alarms Only Terminal.<br><br><strong>Notes:</strong></p><ul><li>If selected, the <strong>Force-arm alarm zone with active alarms</strong> option (below) becomes disabled.</li><li>Without this privilege the force-arm options are not available on the HBUS Terminal or HBUS Alarms Only Terminal.</li></ul></td></tr><tr><td>Force-arm alarm zones with active alarms</td><td><p>If an Alarm Zone would not normally arm because there were any active alarms, by having this privilege and either the "Override" or "Override up to Medium Priority" operator privilege, a user will be provided with the option to force-arm the Alarm Zone, when arming from an HBUS Terminal or HBUS Alarms Only Terminal (as long as doing so will not cause any new alarms).<br><br><strong>Notes:</strong></p><ul><li>If selected, the <strong>Force-arm alarm zone with any alarms</strong> option (above) becomes disabled.</li><li>Without this privilege the force-arm options are not available on the HBUS Terminal or HBUS Alarms Only Terminal.</li></ul></td></tr><tr><td>Isolate alarm zones</td><td>If an Alarm Zone would not normally set because there were open Inputs or a Fence Zone is in alarm, by having this privilege a user will be provided with the option to auto-isolate the Input’s Alarm Zones, when arming from an HBUS Terminal or HBUS Alarms Only Terminal.<br><br><strong>Note:</strong> Without this privilege the auto-isolate options are not available.</td></tr></tbody></table>

</details>

<details>

<summary>Alarm Zones tab</summary>

1. Click the **Alarm Zones** tab.

   This tab provides a grid of Alarm Zones that can be controlled using HBUS Terminals and HBUS Alarms Only Terminals.
2. Click **Configure** from the menu bar, then **Hardware**.

   The **Hardware** List Window opens.
3. Highlight the appropriate HBUS Terminal or HBUS Alarms Only Terminal, and **double-click** the mouse button.
4. Click the **Alarm Zones** tab of the HBUS Terminal or HBUS Alarms Only Terminal.
5. Highlight the Alarm Zones to be managed by this Access Group, and drag and drop them into it’s **Alarm Zones** tab.

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

</details>

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

The Access Group has been updated with the new Alarm Zones and Privileges for HBUS Terminal or HBUS Alarms Only Terminal use.


---

# 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/configuring-access-group-privileges-for-terminal-access.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.
