> 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/alarm-viewer/acknowledging-alarms.md).

# Acknowledging alarms

The coloured bar at the beginning of an alarm flashes if the Alarm is unacknowledged. Acknowledge an alarm by either:

* clicking anywhere on the coloured bar at the beginning of the alarm you want to acknowledge, OR
* clicking on the alarm in the list that you want to acknowledge (so it becomes highlighted), and click the **Acknowledge** button.

  **Note:** The Tiles configured for this Alarm Viewer display in the Viewer Panel below the Alarm List. Any Cardholder Tiles are not editable from this Viewer.

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

* The coloured bar at the beginning of the alarm stops flashing and reduces in size, so it is easy to identify which alarms are still unacknowledged.
* The corresponding coloured block above the Alarm List is selected and expanded.
* An entry is written to the alarm's history.
* The number of unacknowledged alarms changes below the alarm. In this example, it now states *3 Alarm(s), 2 Unacknowledged*.


---

# 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/alarm-viewer/acknowledging-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.
