> 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/alarm-details-tile-actions.md).

# Alarm Details Tile actions

The Alarm Details Tile will display the appropriate details for the configured fields, and can only appear on an Alarm Viewer, Event Viewer or a Spot Monitor Viewer.

Alarm Details will only be displayed in response to selecting an Alarm, so if the user has the privilege to see the Alarm they will be able to see the related Alarm Details.

If the Alarm is for a remote Event Source the name of server will be displayed in the title of the Tile, (i.e. in square brackets following the configured title).

For Flooded Alarms the **Last Occurred** date and time in the Alarm Details reflect the date and time of the most recent flooded entry, and the **No. of Occurrences** indicates the number of individual Alarms included in the flood.

Manually entered Alarm Notes show as an **Alarm History** entry in **bold** text.


---

# 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/alarm-details-tile-actions.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.
