> 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/products/cc-software/configure/alarm-zones/configure-alarm-zones.md).

# Configure alarm zones

Create, connect, and initialize alarm zones.

## Configure alarm zones

An **alarm zone** groups doors, readers, inputs, and fence zones. It manages events and alarm state. Every door, reader, and tamper input needs an alarm zone. Otherwise, events do not log and alarms do not fire.

Use one default alarm zone per controller. Do not span alarm zones across controllers. An offline controller can compromise a multi-controller alarm zone.

{% hint style="info" %}
**Alarm zones are not access zones.** Access zones define physical movement. Alarm zones manage events and alarm responses.
{% endhint %}

### What an alarm zone defines

| Element              | Purpose                                                             |
| -------------------- | ------------------------------------------------------------------- |
| **Division**         | Identifies the owning tenancy.                                      |
| **Controller**       | Identifies the C7000 or C6000 hosting the zone.                     |
| **Members**          | Includes attached doors, readers, inputs, outputs, and fence zones. |
| **Event Defaults**   | Defines operator action plans for zone alarms.                      |
| **State control**    | Defines manual, scheduled, or key-switch arming.                    |
| **Arming behaviour** | Defines force arm, input isolation, or failure to arm.              |

### Create and initialize a zone

1. Go to **Configure → Alarm Zones → New**.
2. Enter the name and division on **General**.
3. Select the controller under **Connections**.
4. Configure event defaults, state changes, and advanced arming behaviour.
5. Apply the configuration.
6. Associate inputs with the alarm zone.

Inputs report state changes. The alarm zone evaluates those changes.

### Installation order

Configure alarm zones after divisions, day categories, schedules, and controllers. Configure them before access zones, doors, readers, inputs, outputs, access groups, and cardholders.


---

# 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/products/cc-software/configure/alarm-zones/configure-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.