> 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-response-plans.md).

# Configure alarm response plans

Choose the right action-plan level for alarm events.

## Configure alarm response plans

Action plans tell operators what to do when an alarm fires. Configure them at the level that matches the response.

| Level                 | Where configured           | Use case                                     |
| --------------------- | -------------------------- | -------------------------------------------- |
| **Server Properties** | Site-wide defaults         | Fallback for events without a specific plan. |
| **Alarm Zone**        | Per alarm zone             | Standard response for zone members.          |
| **Device**            | Per door, reader, or input | Exceptional handling for one device.         |

Put most action plans at the **alarm zone** level. Use server properties as an absolute fallback. Use device-level plans only for justified exceptions.

Action plans configured on an alarm zone apply when its member alarms fire.


---

# 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-response-plans.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.