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

# Configuring Access Group Privileges for Terminal access

This procedure describes how to assign *Alarm Zones\** to an Access Group, and specify associated privileges for Terminal use.

{% hint style="info" %}
**\*Alarm Zones**

A grouping (normally geographical) of alarm points that are set and unset (or in user defined states) at the same times.
{% endhint %}

1. Click on the Access Group you want to assign Alarm Zones to from the list in Viewer Navigation Panel.
2. Click the **Alarm Zone** tab, if not already displayed.
3. In the **Terminal Privileges** section, select the appropriate privileges as required for the Access Group.

<details>

<summary>Click here for a description of what each of the privileges enable members to do</summary>

<table><thead><tr><th width="252">Privilege</th><th>Description</th></tr></thead><tbody><tr><td>View Alarms and items</td><td>This privilege enables a user to view all available alarms and all inputs 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 inputs 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>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).</td></tr><tr><td>- Cancel others lock out</td><td>This privilege enables the <strong>UNLOCK</strong> key on the Terminal so you can cancel the lockout of the selected Fence Zones.<br>This is only possible from the Terminal that was used to put the fence into lockout.</td></tr><tr><td>Prompt for alarm zone selection</td><td>This option is only available if the <strong>Change to the Disarmed state</strong> and/or <strong>Change to the Armed state</strong> options are also checked (in the Alarm Zone Privileges section).<br>This privilege enables a user to view a list of Alarm Zones for which the user has this privilege for, when the <strong>Arm</strong> or <strong>Disarm</strong> key is selected on the Welcome screen of an HBUS Terminal or HBUS Alarms Only Terminal.<br>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>, on an HBUS Terminal or HBUS Alarms Only Terminal.</td></tr><tr><td>Force-arm alarm zones with any alarms</td><td>This option is only available if the <strong>Change to the Armed state</strong> option is also checked (in the Alarm Zone Privileges section). If selected, the <strong>Force-arm alarm zone with active alarms</strong> option (below) becomes disabled.<br>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 a Terminal.<br><br><strong>Note:</strong> Without this privilege the force-arm options are not available on the HBUS Terminal.</td></tr><tr><td>Force-arm alarm zones with active alarms</td><td>This option is only available if the <strong>Change to the Armed state</strong> option is also checked (in the Alarm Zone Privileges section). If selected, the <strong>Force-arm alarm zone with any alarms</strong> option (above) becomes disabled.<br>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 (as long as doing so will not cause any new alarms).<br><br><strong>Note:</strong> Without this privilege the force-arm options are not available on the HBUS Terminal.</td></tr><tr><td>Auto-isolate alarm zones</td><td>This option is only available if the <strong>Change to the Armed state</strong> option is also checked (in the Alarm Zone Privileges section).<br>If an Alarm Zone would not normally set because there were open Inputs, by having this privilege you will be provided with the option to auto-isolate the Input’s Alarm Zones, when arming from the menu of 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>

**Note:** The **Terminal Access** section is for configuring periodic testing, to allow members of the Access Group to disarm the system via a Terminal.

Refer to [Configuring Access Groups for Test Modes](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/access-groups/configuring-access-groups-for-test-modes.md) for further detail.

4. Select the Alarm Zones to be managed by this Access Group, as follows:
   1. Click the **Add Alarm Zones** button.

      A browse tool displays.

      ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-6573eff6259e65b2cc0c6ac613a5546bc3fca0f9%2Fag_addalmzones_popup.png?alt=media)
   2. If necessary, search for the Alarm Zone(s) you want by entering characters in the **Search** field and/or refining the search mode and filters.

      The grid becomes populated with Alarm Zones that match the search criteria.
   3. Check the Alarm Zone(s) you want the group to have access to, and click the **Add Selection** button.

      The browse tool closes, and the selected Alarm Zone(s) appear in the Alarm Zones grid.
5. Click the **Save** button.


---

# 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/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.
