> 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/products/cc-software/reference/server-notifications.md). # Notifications [Server Configuration](/knowledge-hub/products/cc-software/configure/server-configuration.md) › Server - Notifications ## This page answers * How does Command Centre deliver notifications? * How do email and SMS notifications work? * What is the difference between Broadcast Notifications and Mobile Command Centre push? Command Centre can deliver notifications by email, SMS, and mobile push, depending on the notification type and the destination configured for the recipient. Example notifications include competency expiry, arming status of alarm zones, access alerts, site-wide alerts, and server status. There are three main delivery methods: * **Email:** sent through the outgoing SMTP server to the recipient's email address. * **SMS:** also sent through the outgoing SMTP server, but addressed to a third-party SMTP-to-SMS service. * **Mobile push:** sent as a push notification to a Gallagher mobile application. ![Diagram of notification transports in Command Centre, showing email, SMS, and mobile push delivery paths](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-ad1686980c8a5d3364065d4c061af1a25ad0b5b1%2FSECHUB-CCS-SRV-07-notifications-transport-diagram.png?alt=media) > ⚠️ **Important:** Alarm Notifications (Gallagher alarm-generated messages) **cannot** be sent to Mobile Connect users. *** ## Email and SMS notifications Traditional cardholder notifications use a **Notification Filter**: one or more alarms or events are selected in the filter, and the filter is then assigned to a cardholder with notifications enabled. For a cardholder to receive these notifications, the cardholder must have the required **Personal Data Field (PDF)** configured: * **Email** requires a PDF of type **Email**. * **SMS** requires a PDF of type **Mobile**. Email notifications are sent directly through the configured outgoing SMTP server. SMS notifications are **also** sent through the configured outgoing SMTP server. Command Centre does not send them directly to the mobile phone network. Instead, it builds an email address from the cardholder's mobile number plus the SMS domain configured under **File > Server Properties > Mobile/SMS Notifications**, then sends that email through SMTP to a third-party SMTP-to-SMS provider. For example, if the configured SMS domain is `textmagic.com` and the cardholder's mobile number is `+1 234-567-8900`, Command Centre sends the notification to `12345678900@textmagic.com`. The third-party provider receives the email, checks whether the sender belongs to an authorised customer account, and if valid forwards the message through the SMS network to the phone. > **Note:** because SMS delivery relies on SMTP plus a third-party SMTP-to-SMS provider, SMS notifications require **both** the SMTP server and the external service to be configured correctly. > **Note:** Command Centre **9.30+** can deliver outgoing email using **Exchange Online**. Although the connection from Command Centre to Exchange is not strictly SMTP, it behaves as SMTP. If the recipient's email is hosted outside Exchange, final delivery still happens through SMTP. For this document, any mention of SMTP remains valid when Command Centre is configured with Exchange Online. *** ## Broadcast Notifications Broadcast Notifications can be initiated from within Command Centre Client and sent to individual cardholders or groups of cardholders. They support three delivery methods: **Email**, **SMS**, and **Mobile**. * **Email** or **SMS** Broadcast Notifications use the same SMTP-based delivery path as traditional cardholder notifications. Email needs the outgoing SMTP server; SMS needs the outgoing SMTP server plus a correctly configured third-party SMTP-to-SMS service. * **Mobile** Broadcast Notifications are delivered as a push notification to cardholders who use a **Mobile Credential** and have the **Gallagher MC** application installed (also known as **Mobile Connect**). These are sent using the Gallagher cloud service and do **not** require an SMTP server, and do **not** use the SMS network. > **Note:** Broadcast Notification Mobile delivery is intended for cardholders using Mobile Connect. It is separate from SMS delivery, even though both options appear on the same Mobile/SMS Notifications configuration tab. > **Note:** there is no direct way to send a Broadcast Notification to cardholders from a system event alone. However, pre-configured Broadcast Notifications can be automated using **macros**. Command Centre can set up template (canned) messages and configure recipient lists in advance. Coupled with macros, pre-configured Broadcast Notifications can be triggered by any mechanism macros support (item events, scheduled, or repeating), or run manually anywhere the system macros are visible. The **Send Notification** action lets operators send an impromptu Broadcast Notification, for example: * Notify specific security staff to investigate suspicious activity * Warnings for Civil Defence / fire alarm testing * Inform groups about system upgrade notifications * Notify staff of potential hazards in specific zones ![Command Centre Broadcast Notification user interface](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-1ed50db4db71d817d524a199fe8f7de05f1843d5%2FSECHUB-CCS-SRV-08-broadcast-notification-ui.jpg?alt=media) *** ## Notifications to the Mobile Command Centre application Notifications sent to the **Mobile Command Centre** application are push notifications sent from the Command Centre server to the **Gallagher CC** mobile application used by operators. The content is the equivalent of an alarm viewer, on a mobile device. The app does not need to be open, though how visible the alert is depends on the mobile device settings. These are **different** from Broadcast Notification Mobile delivery to Mobile Connect cardholders. Mobile Command Centre push notifications are configured under **File > Server Properties > Mobile/SMS Notifications**, but they do not use the SMTP-to-SMS path. These notifications are pushed to the Mobile Command Centre application **only if the server sending the notification is the last Command Centre server the mobile application connected to.** ### Connecting to multiple Command Centre servers If the user's Mobile Command Centre application connects to multiple servers, connecting to another server breaks the connection to the previous server, preventing the previous server from sending push notifications to that device. A practical example: a user regularly connects to three servers (A, B, C). When connected to **Server A**, they receive push notifications from Server A, but not from B or C. When they later connect to **Server B** or **Server C**, they no longer receive push notifications from Server A. They only receive push notifications from the server they are currently, or most recently, connected to. *** 🔗 **Related** * [Server - Enabling Gmail For Notifications](/knowledge-hub/products/cc-software/configure/server-configuration/server-enabling-gmail-for-notification.md). App passwords and the outgoing/incoming email settings for Gmail. --- # 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/products/cc-software/reference/server-notifications.md?ask=&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.