> 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/broadcast-notification-configuration/quick-tips-for-working-with-broadcast-notifications.md).

# Quick Tips for working with Broadcast Notifications

* When a Broadcast Notification tile is added to a Viewer, an operator with the 'Send Broadcast Notification' privilege can send the same email or SMS message (text message) to many Cardholders at once, (e.g. to warn them of a danger on site, or that the site is in lockdown).
* Before creating a Broadcast Notification, the following must be configured in Gallagher Configuration Client:
  * Notification, Email and SMS Server Properties.

    Refer to *"Notifications", "Outgoing Email", "Incoming Email"* and *"Mobile/SMS Notifications"* in the Gallagher Configuration Client Online Help for the procedures.
  * Command Centre Notifications.

    Refer to *"Setting Cardholder 'Email' and 'Mobile' PDFs"* in the Gallagher Configuration Client Online Help for the procedure.
* Broadcast Notifications with unsaved changes display in the Navigation Panel in **bold** and have a **\*** at the end of their name.
* An Activity Report can be configured to view all Broadcast Notification 'succeeded' or 'failed' events.
* Macros can be configured to send Broadcast Notifications.

  **Note:** A Broadcast Notification item cannot be deleted while it is used in a macro.

### More information

For more information, refer to the topic *"Broadcast Notifications"* in the Gallagher Command Centre Online Help.


---

# 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/broadcast-notification-configuration/quick-tips-for-working-with-broadcast-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.
