> 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-hardware/perimeter-solutions/perimeter-keypads/configure/keypads-viewing-alarms-zones-and-input.md).

# View alarm zones and inputs

View alarm zones and input states, then shunt eligible inputs from a Remote Arming Terminal.

### Procedure

1. Press the **More** key on "Choose Action" to reach the "Main Menu".
2. Scroll to **"Alarm Zones & Inputs"** and press the key. The "Alarm Zones" screen displays.
3. Only Alarm Zones for which the operator has the "view" privilege, associated with this RAT, display.
4. Use the up/down keys to scroll. The LCD shows 5 zones at a time, and a + at the top or bottom indicates there are more.
5. Status indicators: A / D / 1 / 2 / ?, and HV / LF (as on the Arm screen).

### View inputs within an alarm zone

1. Select the Alarm Zone and press the key. The Inputs screen displays.

Input status codes:

| Code | Meaning   |
| ---- | --------- |
| O    | Open      |
| C    | Closed    |
| T    | Tamper    |
| S    | Shunted   |
| ?    | Not known |

### Shunt an input

* Select the input and press the key. **'s' displays beside the input** (shunted).
* To remove the shunt, select an input with 's' and press the key. The current status is shown.
* The Shunt key is not available if the operator has no shunt privilege for this Alarm Zone.

***

🔗 **Related**

* [Keypads - Alarm Input Test modes](/knowledge-hub/products/cc-hardware/perimeter-solutions/perimeter-keypads/configure/keypads-alarm-input-test-modes.md). Test the inputs you can view here.
* [Keypads - Viewing and Acknowledging Alarms](/knowledge-hub/products/cc-hardware/perimeter-solutions/perimeter-keypads/configure/keypads-viewing-and-acknowledging-alar.md). Work the alarm list.


---

# 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-hardware/perimeter-solutions/perimeter-keypads/configure/keypads-viewing-alarms-zones-and-input.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.