> 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-and-acknowledging-alar.md).

# View and acknowledge alarms

View alarm details and acknowledge eligible alarms from a Remote Arming Terminal.

**Required:** the "View Alarms" operator privilege, to access the Alarms option from the RAT main menu.

**RAT beep on alarms:** RATs can be configured to beep when alarms are in the system. This is configured via a checkbox on the Advanced tab of the RAT properties in Command Centre.

### Procedure

1. Press the **More** key on "Choose Action" to reach the "Main Menu".
2. Scroll to **"Alarms"** and press the key.
3. Alarms are collected, **sorted by priority then timestamp**, and the alarm list displays.
4. Use the up/down keys to scroll. The LCD shows 5 alarms at a time, and a + at the top or bottom indicates there are more.

![RAT alarm list, priority and timestamp ordering](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-2d27c5b8d93d80920d9b56a50aaaf3ac2ed9b457%2FSECHUB-RAT-ALARMS-01-alarm-list.png?alt=media)

### Alarm status symbols

| Symbol   | Meaning                         |
| -------- | ------------------------------- |
| `*`      | Active / unacknowledged alarm   |
| `=`      | Active / acknowledged alarm     |
| *(none)* | Inactive / unacknowledged alarm |

> ⚠️ **Important - the alarm list is a snapshot, not live.** The alarm list is captured at the time it opens. It does **NOT** dynamically update as alarms are acknowledged or new alarms are generated in Command Centre. Refresh by leaving and re-entering the Alarms view.

### Acknowledge an alarm

1. Select an individual alarm and press the key. The alarm detail screen displays.
   * **"Active"** after the time means Active / unacknowledged.
   * **"Act/Ack"** after the time means Active / acknowledged (the Acknowledge key is not available because it is already acknowledged).
   * **Nothing after the time** means Inactive / unacknowledged.
2. Press the **Acknowledge** key.
3. The screen returns to the alarm list, and **the alarm is immediately removed from the list**.
4. When acknowledged at the RAT, the acknowledgement is reflected in the Command Centre Alarm window. The alarm no longer flashes and the Acknowledge button is disabled.

***

🔗 **Related**

* [Keypads - Viewing Alarms Zones and Inputs](/knowledge-hub/products/cc-hardware/perimeter-solutions/perimeter-keypads/configure/keypads-viewing-alarms-zones-and-input.md). Inspect the zones and inputs behind an alarm.
* [Keypads - Remote Arming Terminal operation](/knowledge-hub/products/cc-hardware/perimeter-solutions/perimeter-keypads/configure/keypads-remote-arming-terminal-operati.md). The System Summary shows the outstanding alarm count.


---

# 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-and-acknowledging-alar.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.