> 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/site-plan-viewer/displaying-the-alarm-list-on-site-plans.md).

# Displaying the Alarm List on Site Plans

The alarm list is revealed by clicking the ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-17b6cc2715351497a2b9301cc1753d512e841097%2Fsiteplanviewer_alarmlistbutton.png?alt=media) **Alarm** toggle control.

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

The alarm list is restricted to "site item" alarms, and is another way of locating an item in the list, in particular, an item that needs attention.

**Note:** There are no processing options in the list.

### Selecting items from the Alarm List

The result of clicking on an alarm in the Alarm List is determined by whether or not the item in alarm exists on any Site Plan, as follows:

<table><thead><tr><th width="202">If the item...</th><th>then...</th></tr></thead><tbody><tr><td>exists on any Site Plan,</td><td>the item is displayed on any Site Plan (if it exists) with item menus displayed. While the item and item menu are displayed, the list will roll back/hide until the item is deselected or the action has been taken (closing the item menu).<br>A specific Site Plan will display if selected, or display any Site Plan as an item on another Site Plan as selected from the result list.</td></tr><tr><td>does not exist on any Site Plan,</td><td>an Alarm details panel will display to allow you to complete required actions.</td></tr></tbody></table>

### Hints

{% hint style="info" %}
The size of the text can be adjusted by clicking on ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-23f64398526e9351c6ffac93a84270dd8fb2b896%2Ftextsize.png?alt=media) and then dragging the indicator that displays as necessary.
{% endhint %}

{% hint style="info" %}
The **Count** column (if configured to display), indicates either:

* the flood count for an alarm flood. Only one instance of an alarm flood will display, with the flood count for each alarm flood, or
* the number of times a stateful alarm has occurred.

An operator should be able to distinguish these two scenarios by looking at the event history in the Alarm Details Tile.
{% endhint %}


---

# 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/site-plan-viewer/displaying-the-alarm-list-on-site-plans.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.
