> 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/command-centre-client/using-command-centre/working-with-viewers/tile-actions/site-plan-tile-actions/viewing-alarms.md).

# Viewing Alarms

When an item is in alarm, the details of the alarm can be viewed via a context menu, as follows:

1. Click on the item's icon.

   A context menu displays.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-c6ccc989faab1e243870284904f513e6611cf6b5%2Fsiteplan_iconalarm.png?alt=media)
2. Click **View Alarm...** from the context menu.

   An Alarm Properties pop-up displays for the item.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-d711e22afc999f63a1e6e86e292f84ed507bd057%2Fviewalarm_popup.png?alt=media)

   This pop-up provides details and history of the Alarm, and Alarm Instructions if applicable. If there is more than one Alarm for the selected item the **Previous Alarm** and **Next Alarm** buttons are enabled, allowing you to navigate through all the Alarms for the item without returning to the Tile.
3. Take the appropriate action, as follows:

   <table><thead><tr><th width="184">To...</th><th>then...</th></tr></thead><tbody><tr><td>enter an Alarm Note</td><td><ol><li>Select the appropriate Alarm Note(s) via the function keys indicated.</li><li>Optionally enter any comments in the <strong>Comments</strong> field.</li><li>Acknowledge and/or process the Alarm, as appropriate.</li><li>You can save Alarm Notes (and comments) without having to acknowledge or process an alarm, using the <strong>Close</strong> button.</li></ol></td></tr><tr><td>acknowledge the alarm</td><td>click the <strong>Acknowledge</strong> button.<br>If there is only one Alarm for the item, the Alarm Properties pop-up closes. If there is more than one, the Alarm remains on screen so you can navigate to the next/previous Alarm using the <strong>Previous Alarm</strong> and <strong>Next Alarm</strong> buttons. The unacknowledged Alarm count (top right corner of pop-up) reduces as applicable.</td></tr><tr><td>process the alarm</td><td>click the <strong>Process</strong> button.<br>If there is only one Alarm for the item, the Alarm Properties pop-up closes. If there is more than one, the next Alarm displays automatically and the "Alarm of" count (top right corner of pop-up) reduces, otherwise the current Alarm should remain on screen so the user can navigate to the next (or previous) Alarm.</td></tr></tbody></table>


---

# 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/command-centre-client/using-command-centre/working-with-viewers/tile-actions/site-plan-tile-actions/viewing-alarms.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.
