> 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/alarm-viewer/entering-an-alarm-note.md).

# Entering an Alarm Note

Alarm notes can be entered when acknowledging or processing alarms, using the following procedure:

**Note:** Alarm notes default to voluntary, but they can be compulsory for "process only" or "acknowledge and process" if the Operator Groups are configured that way in Configuration Client. In this case, the Enter an Alarm Note pop-up will automatically appear depending on the configuration.

1. Click on the row of the alarm you want to add a note to, so it becomes highlighted.
2. Click the **Add Note** button.

   The Enter an Alarm Note pop-up displays.

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

   **Notes:**

   * The buttons that appear on the Enter an Alarm Note pop-up depends on what action has already been taken, e.g.
     * If the alarm has already been acknowledged only a **Process** button appears.
     * If the alarm has been acknowledged and is active, neither the **Acknowledge** or **Process** buttons appear.
     * If the alarm is active but has not been acknowledged only an **Acknowledge** button appears.
   * If multiple alarms are selected the number of alarms selected will appear in brackets beside the title of the 'Enter an Alarm Note' pop-up.
3. Select the appropriate **Alarm Note(s)**, and optionally enter details of what action you have taken in the **Comments** field.

   **Notes:**

   * As soon as one Alarm Note is selected, or you begin typing in the **Comments** field, the **Process** button changes to **Process with Note**, or if the **Acknowledge** button is displayed, it will change to **Acknowledge with Note**.
   * Alarm Notes can be selected either by checking the checkbox beside the Note, or via function keys. By default, < **F1** > to < **F8** > are assigned to match the first eight alarm notes.

     If a function key that has no matching Alarm Note is pressed, then nothing happens.
4. Click the appropriate button, as follows:

   <table><thead><tr><th width="202">If you click the...</th><th>then...</th></tr></thead><tbody><tr><td><strong>Add Note</strong> button</td><td><ul><li>the Enter an Alarm Note pop-up closes,</li><li>the Note is added to the alarm, and</li><li>the alarm remains in the Alarm List.</li></ul></td></tr><tr><td><strong>Acknowledge with Note</strong> button</td><td><ul><li>the Enter an Alarm Note pop-up closes,</li><li>the Note is added to the alarm, and</li><li>the coloured bar at the beginning of the alarm stops flashing and reduces in size, indicating that the alarm is acknowledged.</li></ul></td></tr><tr><td><strong>Process with Note</strong> button</td><td><ul><li>the Enter an Alarm Note pop-up closes,</li><li>the Note is added to the alarm, and</li><li>the alarm is processed and disappears from the Alarm List.</li></ul></td></tr></tbody></table>

   **Note:** Manually entered Alarm Notes are shown as bold in the **Alarm History** on the Alarm Details Tile.


---

# 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/alarm-viewer/entering-an-alarm-note.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.
