> 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/licensable-features/advanced-alarm-management-feature/alarm-distribution-assignment.md).

# Alarm Distribution/Assignment

Alarms are assigned fairly amongst active operators, taking into consideration the permissions of the operator, and are redistributed if an operator logs off.

### Operator availability

Operators will have the option to start and stop receiving alarms if they:

* are a member of an Operator Group that has the allow alarm assignments setting enabled, and
* have the permission to edit alarms.

Operators can change their availability by selecting the appropriate option from the **Operator Status** drop-down on the Alarm List toolbar, (i.e. either 'Available' or 'Unavailable').

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

Upon first recognising a session, the operator availability service registers operators in the system.

<table><thead><tr><th width="216">When an operator is...</th><th>the operator availability service will...</th></tr></thead><tbody><tr><td>Available,</td><td><ol><li>Add the operator to the alarm queue, and perform alarm assignments.</li><li>An event will be generated when an operator changes their status to Available.</li></ol></td></tr><tr><td>Unavailable,</td><td><ol><li>Remove the operator from the alarm queue.</li><li>Remove any unacknowledged alarms from their assignments, and place those unacknowledged alarms into the alarm queue, and perform alarm assignments.</li><li>An event will be generated to show an operator has changed their status to Unavailable.</li></ol></td></tr><tr><td>Gone from the system in some manner, (e.g. operator logged out of Command Centre without changing their status to Unavailable),</td><td><ol><li>Remove the operator from the alarm queue.</li><li>Un-acknowledge any acknowledged alarms, and unassign all alarms.</li><li>Place the alarms back into the alarm queue, and perform alarm assignments.</li></ol></td></tr></tbody></table>


---

# 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/licensable-features/advanced-alarm-management-feature/alarm-distribution-assignment.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.
