> 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/arm-and-disarm-alarm-zones.md).

# Arm and disarm alarm zones

Select state control and arming behaviour.

## Arm and disarm alarm zones

### State control modes

Choose how the alarm zone arms and disarms.

| Mode                      | Behaviour                                                            |
| ------------------------- | -------------------------------------------------------------------- |
| **Manually Controlled**   | An operator, or a badge holder with disarm privilege, changes state. |
| **Schedule Controlled**   | A schedule automatically arms and disarms the zone.                  |
| **Key-Switch Controlled** | A physical key switch changes the zone state.                        |

Schedule control often uses manual override. For example, a zone can arm at 18:00 and disarm at 06:00. An operator can still change state when needed.

### Arming behaviour

Choose what happens when an input is unsealed at arm time.

| Behaviour          | Effect                                                                        |
| ------------------ | ----------------------------------------------------------------------------- |
| **Force arm**      | Arms with unsealed inputs. Use it where false unseals are common.             |
| **Isolate inputs** | Arms and temporarily isolates unsealed inputs. Inputs re-include when sealed. |
| **Fail to arm**    | Refuses to arm until every input is sealed.                                   |

Use **Fail to arm** for most high-security perimeter zones. A tamper condition then requires investigation before arming.


---

# 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/arm-and-disarm-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.