> 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/event-priorities.md).

# Event Priorities

### Introduction

There are 10 levels of messages within the Command Centre system. Each level is allocated a logical name, colour and alarm sound (optional); you can change these from their defaults.

You also set which message level is the lowest alarm priority. Those levels above the indicator will generate an alarm, those levels below the indicator will generate an event message.

### 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 **Event Priorities** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-154731ecc5941d5e3831f4c82e15abd953304788%2Falmpriority.png?alt=media)
3. Move the mouse pointer to the **indicator** on the Alarm States bar. Click and hold down the mouse button. Drag the indicator to point to the **lowest alarm priority** you want to generate an actual alarm.

   **Note:**

   The indicator will only allow a minimum of two event priorities and one alarm priority.
4. To change the message level **name**, click within the appropriate edit box and **edit the text** as required.
5. To change the **colour**, click on the **colour palette icon** ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-16891b96c9c88f6905a1b5cadc81f459ad453624%2Fcolour.png?alt=media) beside the appropriate message.

   From the displayed colour swatch select the **required colour** to represent the event priority and click **OK**.

   The drop-down menu boxes beside each message level display "Default Sound", which will be used for alarm sounds.

   **Notes:**

   * An alarm sound is optional, therefore "No Sound" is the other option in the list.

     Note though that if two alarms occur and the lower priority alarm has an alarm sound configured, but the higher priority alarm has "No Sound" configured for that event priority, then no alarm sound will play. Therefore, we recommend that you do NOT turn off alarm sounds for an event priority if there are lower event priorities that have an alarm sound configured.
   * The 'Message Only' and 'Not an Event' priorities cannot have alarm sounds configured as they can never be alarms.
6. If you want to change the alarm sound for a particular message level, click the corresponding **Sound File Browse** ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-2faa7ab66c6abaa3b468de2eb70428ff3cce64c5%2Fthreedotsbutton.png?alt=media) button.

   A **Select Audio File** dialog displays showing only **WAV files** ( **\*.wav** ) as they are the only file type that can be used for alarm sounds.
7. Path your way to the appropriate audio file and click the **Open** button.

   The name of the audio file displays in the corresponding sound file name drop-down list.

   **Note:** Any **WAV files** ( **\*.wav** ) selected should:

   * have a play time of no more than two seconds, as the Alarm Viewer replays an alarm sound every two seconds. Very short files, (e.g. that say "Duress", or "Critical", or play only a few notes) are ideal.
   * be PCM format. If you select a non-PCM format WAV file, the following error message displays:

     *"Sound file must be PCM format."*
   * be less than 500KB in size. If you select a **\*.wav** file over this size the following error message displays:

     *"The file cannot be loaded as it exceeds the limit imposed by the system."*
8. To listen to a selected alarm sound before confirming your selection, click the **Sound Preview** ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-3606077d2e06a6feae3d08f2fca4a1bdd7972f7b%2Fsoundbutton.png?alt=media) button to play the corresponding sound.

   **Note:**

   If an alarm sound has a play time of more than two seconds, when you preview it here it will play from start to finish.
9. 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.


---

# 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/event-priorities.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.
