> 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-installation/server-properties/alarm-notes.md).

# Alarm Notes

### Introduction

This tab enables operators with the “Edit Site” (or higher) operator privilege to configure mandatory alarm notes. All fields will be ‘read-only’ for operators with the “View Site” operator privilege.

The Alarm Notes are configured by default, and they are optional by default. If your site does not wish to use Alarm Notes they can all be removed from here.

Enabling alarm notes ensures that operators record notes against specific types of alarms before acknowledging, processing or quick processing them.

### Procedure

1. Open the **Command Centre Server Properties** window. [How?](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/opening-the-server-properties-window.md)
2. Click the **Alarm Notes** tab.

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

   By default, the **Alarm Notes** listbox is populated with six pre-defined alarm notes.

   **Notes:**

   * When you select an alarm note from the **Alarm Notes** listbox, the selected text displays in the textbox below it (as shown in the above screen shot). If you change the textbox contents, the changes are immediately updated in the **Alarm Notes** listbox.
   * For alarm notes that are too long to fit within the listbox, a tooltip displays when you move the mouse over them.
3. To add a new alarm note to the list, either:
   * **right click** anywhere within the **Alarm Notes** field, and select **Insert** from the context menu, or
   * click the **New** button.
4. To delete an alarm note, select the alarm note you want to delete, and either:
   * **right click** and select **Remove from list** from the context menu, or
   * press the < **Delete** > key on your keyboard.
5. Sort the **Alarm Notes** list if required.

   This is done by selecting an alarm note you want to move up or down the list, and clicking the appropriate **arrow** button to the right of the list box.
6. 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.

**Note:**

At least two alarm notes are required in the Alarm Notes listbox, if one or more Operator Groups has a "Required alarm notes" option set on the **Configuration** tab (see [Setting up Operator Groups](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/operator-groups/setting-up-operator-groups.md)), otherwise the following error message displays on saving the changes:

*"At least two alarm notes required for Operator to acknowledge or process alarms."*


---

# 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-installation/server-properties/alarm-notes.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.
