> 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/configuring-command-centre/configuring-licensable-features/mobile-client-configuration/mobile-notifications.md).

# Mobile Notifications

### Introduction

Enabling Mobile Notifications allows a Command Centre site to send alarm notifications to Mobile Client users. Selecting a notification allows the user to view the alarm's details within the Mobile Client.

Only alarm notifications from the most recent Command Centre site that the Mobile Client user has logged into will be sent. Only alarms are sent as Mobile Notifications, not events.

Mobile Notifications use the *Notifications Filters* and *Notifications Schedules* to determine who receives the notifications and when. For details on how to configure Mobile Notifications, refer to the chapter *"Notifications"* in the Configuration Client Online Help.

**Notes:**

* Mobile Connect users **cannot** be sent Alarm Notifications, they can be sent Broadcast notifications.

  Only operators can be sent Alarm notifications, so only to the Mobile Command Centre App, not the Mobile Connect.
* If you receive notifications from Site A, and then you log into Site B (that doesn't have Mobile Notifications enabled), you will continue to receive notifications from the previous site (Site A).
* If multiple alarm notifications are generated while your device is powered off, or otherwise unable to connect to the internet, then upon reconnection you may only receive a notification for the most recent alarm. This limitation is imposed by iOS and Android. Open the 'Alarm List' screen within the App to ensure you are aware of all the alarms that have occurred.

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

### How are they sent?

Mobile Notifications are sent over the internet, using Wi-Fi or cellular data. Hence a Mobile Client user will continue to receive notifications (via cellular data), if Wi-Fi connectivity for the Mobile Client is unavailable.

If the Command Centre Cloud is offline or the internet is down, notifications are queued in Command Centre awaiting delivery to the cloud when conditions allow. If a queued alarm has been processed by an operator it will not be sent to the cloud.


---

# 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/configuring-command-centre/configuring-licensable-features/mobile-client-configuration/mobile-notifications.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.
