> 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-monitoring/alarm-input-test-modes/configuring-inputs-for-test-modes.md).

# Configuring Inputs for Test Modes

### Introduction

This procedure describes how to configure each input that requires testing.

**Note:** The normal state of all inputs should be 'closed'. If an input is 'open' you will need to reverse the state of the input, by checking the Input is inverted checkbox on the **Advanced** property page for the input.

### Procedure

1. Click **Configure** from the menu bar, then **Hardware**.

   The **Hardware** List Window opens (in [tree view](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/tree-view.md)).
2. **Right click** on the appropriate Input and select **Properties**.
3. Click the **Event Response** tab.
4. If the input requires a visual indication that it is working, (e.g. a light turns on when the input is activated) assign an Action Plan to the Open/Off Event Group.

   This Action Plan will need to trigger the light when the input changes state.
5. Assign a primary Alarm Zone for all events from the drop-down list.
6. Click the **Testing** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-b688b65a0955b58a3d882b155ba6f86e2e5ab9f3%2Finput_testingtab.png?alt=media)
7. If the input requires periodic or manual testing, check the **Include in Alarm Zone Input tests** checkbox.

   The input will be included in all periodic and manual tests.
8. If the input requires mask testing, check the **This Input must be triggered at least once every X days** checkbox and enter the number of days the input must be activated within.

   (Default = 7 days. Configurable from 1 to 30 days.)
9. If the input is a seismic detector, check the **Input must trigger during pre-arm** checkbox.
10. Click the **OK** button to exit and save your changes.
11. Repeat this procedure for each input that requires testing.


---

# 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-monitoring/alarm-input-test-modes/configuring-inputs-for-test-modes.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.
