> 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/alarm-zone-tab.md).

# Alarm Zone tab

This procedure describes the configuration on the **Alarm Zone** tab for an Access Group.

1. Click the **Alarm Zone** tab.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-d9dd0ca1d5c28696d05ff724d0737705975deb79%2Faccessgroups_alarmzonetab_v840.png?alt=media)
2. Add **Alarm Zones** appropriate for 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-aaeb76b81e0d1cd909097eaa86b7f5c9e60063a9%2Fselectalarmzone_popup.png?alt=media)
   2. Click the checkbox next to each Alarm Zone name you want to include, or click the **Select All** button if you want to include all Alarm Zones.
   3. Click the **Add Selection** button.

      The pop-up closes and each of the selected Alarm Zone(s) appear in the **Alarm Zones** grid.

   **Note:** To remove an Alarm Zone, select (highlight) the Zone you want to remove and click the **Remove** button.
3. Select the **Alarm Zone Privileges** required for this 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="216">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.<br>When checked, the <strong>Prompt for alarm zone selection</strong> option becomes enabled.</td></tr><tr><td>Change to the Armed state</td><td>arm Alarm Zones associated with any Access Zone associated with the Access Group.<br>When checked, the <strong>Alarm Zone State Options</strong> below become enabled.</td></tr><tr><td>- Prompt for alarm zone selection</td><td>With this privilege selected, a list of all the available Alarm Zones will be provided on the Terminal.</td></tr><tr><td>- Force-arm alarms 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 a Terminal.<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 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 a Terminal (as long as doing so will not cause any new alarms).<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 Terminal.</li></ul></td></tr><tr><td>- Auto-isolate alarm zones</td><td>If an Alarm Zone would not normally set because there were open Inputs, by having this privilege you can go to the "Arm Failed" menu on the Terminal and isolate the Inputs so that the Alarm Zone will arm, by pressing the <strong>ISOLATE</strong> key.<br><strong>Note:</strong> Without this privilege the <strong>ISOLATE</strong> key is not available on the "Arm Failed" menu.</td></tr><tr><td>Change fence to 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>

</details>

**Note:** The **Terminal Privileges** and **Terminal Access** sections of this tile relates only to *Terminals\**. Therefore, the privileges and access options should only be selected if your site has Terminals installed and this Access Group will be using them.

Refer to [Configuring Access Group Privileges for Terminal Access](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/access-groups/configuring-access-group-privileges-for-terminal-access.md) and/or [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) as appropriate, for further detail.

{% hint style="info" %}
**\*Terminals**

A Terminal, (i.e. either a Remote Arming Terminal or a T20) can be used by suitably authorised Command Centre operators to perform many of the alarm management operations normally available only from Command Centre workstations. Terminals are connected to Controllers.
{% endhint %}

4. Return to Step 6 of [Creating a new Access Group](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/access-groups/creating-a-new-access-group.md) for configuration instructions for the other Access Group tabs.


---

# 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/alarm-zone-tab.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.
