> 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/configuration-scenarios/scenario-alarm-zone-testing.md). # Test alarm zones Test alarm zones without generating alarms or sending monitoring messages. When technicians are on site, you usually want to test alarm zones **without** generating alarms or sending messages to monitoring. Every alarm zone can be overridden into **four states**, but most sites only use the first two (Armed, Disarmed). Rename the third state to **Testing** in Server Properties and give it an action plan that produces a **Message only** with **no Alarm Transmitter** selected. A technician can then put the zone into Testing and work without raising alarms. ### The four alarm zone states Most people do not notice that every alarm zone can be overridden into **four** states; most sites only use the first two. ![Alarm zone showing the four override states](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-15d7d279e2f3bc4e3b850558b9ed4ae804c9858e%2FSECHUB-CCS-ALARMTEST-01-four-states.png?alt=media) The names of the third and fourth states are set **site-wide** in **Server Properties**. You can change them to anything you like. ![Server Properties where the state names are set](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-02f500157d3655323f2bd99aac9e813923cd32e3%2FSECHUB-CCS-ALARMTEST-02-server-properties.png?alt=media) In this example the **third state has been changed to "Testing"**. ![Third state renamed to Testing](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-42d646a90a6c8ac4f22746d03d542056b52f256c%2FSECHUB-CCS-ALARMTEST-03-testing-state-renamed.png?alt=media) ### Configure the Testing state On an action plan you now see the change: a **Testing** option is present instead of "User1". ![Action plan now showing the Testing option](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-6abca74ad899c2b9a11be882ceea218bc9a71e70%2FSECHUB-CCS-ALARMTEST-04-action-plan-testing-option.png?alt=media) ![Armed status action plan configuration](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-90fbe8cef61d8bebbcfbb2f798ca34985cb30f82%2FSECHUB-CCS-ALARMTEST-05-armed-config.png?alt=media) ![Testing status set to Message only with no Alarm Transmitter](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-3d4dd24cdf98cdfe039e048eb89151d3b1364b3c%2FSECHUB-CCS-ALARMTEST-06-testing-message-only.png?alt=media) In both the **Armed** and **Disarmed** statuses there are alarms being generated and messages being sent to the IP Alarm Transmitter. But the **Testing** status has **Message only** and **no Alarm Transmitter** selected. This means a technician can put the alarm zone into the Testing state and carry out tests around the site **without** generating alarms in the system or sending messages to monitoring. > **The third and fourth alarm zone states can only be overridden from Command Centre, not from a terminal.** ### Related links * [Alarm Transmission - Monitoring](/knowledge-hub/products/cc-software/configure/alarm-transmission/alarm-transmission-monitoring.md). How action plans and the Alarm Transmitter send events to monitoring. --- # 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/configuration-scenarios/scenario-alarm-zone-testing.md?ask=&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.