> 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/alarm-viewers/changing-the-alarm-viewer-behaviour.md).

# Changing the Alarm Viewer behaviour

### Introduction

The behaviour of the Alarm Viewer window can be configured via the **Configuration** tab of an [*Operator Group*](https://help.security.gallagher.com/knowledge-hub/configuration-client/glossary-of-terms.md#operator-group) properties. Therefore, the Alarm Viewer window will behave the same for all operators in an Operator Group.

The options for how the Alarm Viewer window will behave are:

* The Alarm Viewer will remain wherever it is placed by the currently logged on operator, and does not pop to the front of other windows.
* The Alarm Viewer will always be in front of all other windows.
* The Alarm Viewer will be made visible and brought to the front of all other windows when a new alarm occurs.

### Procedure

1. Click **Manage** from the menu bar, then **Operator Groups**.

   The **Operator Group** List Window opens (in [grid view](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/grid-view.md)).
2. **Highlight** the appropriate Operator Group.
3. **Right click** the mouse button, and select **Properties**.
4. Click the **Configuration** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-cc461b5989541538774abc0f1ce1c25797a09240%2Fogconfig.png?alt=media)
5. If you want the Alarm Viewer to remain wherever it is placed by the currently logged on operator, and not to automatically pop to the front of other windows, then ensure the **Alarm Viewer Configuration** checkbox is unchecked.

   Go to Step 8.
6. Check the **Alarm Viewer Configuration** checkbox.
7. Click the appropriate radio button for the option you prefer.

   <table><thead><tr><th width="222">Option</th><th>Description</th></tr></thead><tbody><tr><td>Automatically displays on alarm occurrence</td><td>The Alarm Viewer will be opened, made visible and brought to the front of all other windows on the occurrence of any new alarm.<br>With this option enabled you can not locate the Alarm Viewer off screen and the entire Alarm Viewer will be visible at all times.</td></tr><tr><td>Always on top</td><td><p>The Alarm Viewer will always be in front of all other windows.<br>With this option enabled the entire Alarm Viewer will be visible at all times and you can not:</p><ul><li>minimise the Alarm window, or</li><li>locate the Alarm window off screen.</li></ul></td></tr></tbody></table>
8. Do you want escalated alarms to display in a separate window from the main Alarm Viewer?

   <table><thead><tr><th width="84">If...</th><th>then check the...</th></tr></thead><tbody><tr><td>yes</td><td><strong>Enable Escalated Alarm Viewer</strong> checkbox. The Escalated Alarm Viewer will be accessible from the <strong>Monitor</strong> menu, as well as the main Alarm Viewer.</td></tr><tr><td>no</td><td><strong>Leave escalated alarms in main Alarm Viewer</strong> checkbox. Any escalated alarms will remain in the main Alarm Viewer with non-escalated alarms.</td></tr></tbody></table>

   **Note:** By checking both options you can have escalated alarms appear in both the main Alarm Viewer as well as the Escalated Alarm Viewer.
9. Check the **Do not allow operator to acknowledge or process escalated alarms** checkbox if required for this group.

   **Note:**

   If checked, the **Acknowledge** and **Process** buttons will be disabled on the Alarm Details property page for escalated alarms.
10. Do you wish to configure alarm note options?

    If **no**, then go to Step 11.

    If **yes**, then click the appropriate radio button for the option you require.

    * **Optional**

      The privileged operator can optionally select alarm note(s) before processing or acknowledging an alarm.
    * **Required when processing alarms**

      The privileged operator must select one or more alarm notes in order to process, or bulk process alarms at a priority level that is equal to or higher than the alarm notes priority threshold.
    * **Required when acknowledging or processing alarms**

      The privileged operator must select one or more alarm notes in order to acknowledge, process or bulk process alarms at a priority level that is equal to or higher than the alarm notes priority threshold.
11. Click **OK** to exit and save your changes.

    Click **Cancel** to exit without saving your changes.

    Click **Apply** to save your changes and stay in this window.

### Result

The behaviour of the Alarm Viewer window has been altered accordingly.


---

# 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/alarm-viewers/changing-the-alarm-viewer-behaviour.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.
