> 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/configuration-client/site-monitoring/site-plans/viewing-alarms-from-site-plans.md).

# Viewing Alarms from Site Plans

### Introduction

When an item, (e.g. a shape, icon, etc., indicating either a linked Site Plan or another item), on a Site Plan starts flashing, this indicates an alarm has occurred. When this happens, you can view the alarms directly from the Site Plan, and acknowledge and process them accordingly.

**Note:** If a linked Site Plan in alarm was created in Command Centre Client, the following message will display when you try to open it using this procedure:

*"This site plan is edited or viewed in the Command Centre Client"*

### Procedure

#### Viewing linked Site Plans in Alarm

Either:

* **Right click** on the flashing linked Site Plan item and select **View Site Plan with Alarm**.

  The Site Plan window automatically navigates straight to the Site Plan containing the most important alarm, skipping any intermediate Site Plans. You can then view the actual alarm on the site item (see below).

Or:

* **Double click** on the flashing linked Site Plan item.

  The Site Plan indicated by the link will display, enabling you to work your way forward to the actual alarm, but see each of the linked Site Plans as you go.

#### Viewing site items in Alarm

Either:

* **Right click** on the flashing item and select **View Alarm**.

Or:

* **Double click** on the flashing item.

  The most important Alarm Properties page for the site item displays.

  **Notes:**
* Double-clicking on a flashing icon from here or from the Status Viewer results in the Alarm Properties page for the item opening. Whereas, double-clicking on an item in alarm from a List Window or from the Find Tool results in the items Property pages opening.
* When **View Alarm** is selected on a Site Plan and the ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-c1a6e386f72d3952c160c0384d6c2fd9e56caeab%2Fviewnextalarm.png?alt=media) checkbox is checked, the alarm next viewed will be the next in decreasing priority/time related to the Site Plan.

### Hints

{% hint style="info" %}
**Alarms in the Site Plan List Window**

Site Plans in alarm will flash on the **Site Plan** List Window also. If the Site Plan that is in alarm is a child Site Plan, the parent Site Plan will flash also.

The **View Site Plan with Alarm** and **View Alarm** options are available directly from the **Site Plan** List Window, by right clicking on the Site Plan in alarm, and selecting the required option from the pop-up menu.
{% endhint %}

{% hint style="info" %}
**Acknowledging Alarms**

Site Plan items stop flashing and go solid in colour once the alarm is acknowledged.

For more information on acknowledging and processing alarms, see [Alarm Viewer](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-monitoring/alarm-viewers.md).
{% 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/configuration-client/site-monitoring/site-plans/viewing-alarms-from-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.
