> 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-installation/alarm-zones/understanding-alarm-zones.md).

# Understanding Alarm Zones

An Alarm Zone is a grouping of objects or entities whose states need to be armed and disarmed together.

**Example 1 -&#x20;*****Localised Zone:***

When a staff member presents their card, they gain access to a specific [*Access Zone*](https://help.security.gallagher.com/knowledge-hub/configuration-client/glossary-of-terms.md#access-zone) and the associated Alarm Zone is automatically disarmed. All the PIRs in that zone are deactivated, however PIRs in other Alarm Zones will be unaffected. At the end of the day the last person in the Alarm Zone can then arm the zone.

**Example 2 -&#x20;*****Site wide zone:***

Doors entering a stairwell on each level are controlled by the Controller(s) on that floor. The Alarm Zone is spanned across multiple Controllers since the sensors for the various doors are on different Controllers. This Alarm Zone, although not recommended, can be spanned across multiple Controllers. See 'Alarm Zones shared across multiple Controllers' below for further detail.

The Alarm Zones can be set up to change automatically (via the [*Schedule*](https://help.security.gallagher.com/knowledge-hub/configuration-client/glossary-of-terms.md#schedule)) or manually (via a keyswitch or override from a Gallagher keypad reader).

### Alarm Zones shared across multiple Gallagher Controllers

Alarm Zones are known to operate reliably when shared (spanned) across multiple Controllers. If however one or more of the Controllers go offline due to network failure, then the Alarm Zone will remain in the state it was in when the Controller(s) went offline. Any manual Alarm Zone overrides attempted during this time will fail. This manual state change can be reapplied once the Controller(s) are back on line.

If an Alarm Zone state change is scheduled, and the Controller(s) is offline, then the Alarm Zone state will remain unchanged until all of the Controller(s) sharing that Alarm Zone are back on line; in which case the Alarm Zone will change to the scheduled state within 60 seconds.

### Arming Alarms Zones using the T20 Terminal

It is not possible to collectively or individually arm Alarm Zones in User 1 or User 2 state from a T20 Terminal without disarming the Alarm Zones first. When arming all Alarm Zones (of which some zones are in User 1 or User 2 state), the User 1 and User 2 zones will not be armed.

### Terminology

Your system is configured to display your preferred terminology regarding Alarm Zones (Armed/Disarmed OR Set/Unset). Refer to [Alarm Zone States](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/alarm-zone-states.md) within Server Properties.

### Alarm Zone States

There are different icons for the states of Alarm Zones, so you can see from this window what state an Alarm Zone is in, depending on how you have your icon set configured, (e.g. green for disarmed, red for armed, white for unknown, etc.). Opening the **Icons** tab of an Alarm Zone's properties shows the different icons for each state.

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

For each Alarm Zone state you can select different priorities, outputs to switch and escalation times.

*Set / Armed*\
In this mode the alarms are set. The alarm will be triggered if inputs change state and/or device events are generated. This can be considered the active state for the Alarm Zone.

*Unset / Disarmed*\
In this mode the alarms are unset.

*User 1 and User 2*\
If required, you can set up these additional two Alarm Zone states to suit.


---

# 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-installation/alarm-zones/understanding-alarm-zones.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.
