> 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/working-with-viewers/tile-actions/broadcast-notification-tile-actions.md).

# Broadcast Notification Tile actions

Broadcast Notifications are sent from the Broadcast Notification Tile.

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

### Operator Privileges

<table><thead><tr><th width="300">Privilege</th><th>Is required to...</th></tr></thead><tbody><tr><td>View Site</td><td>view Broadcast Notification items.</td></tr><tr><td>Send Broadcast Notification</td><td>to send a Broadcast Notification.</td></tr><tr><td>View Cardholders</td><td>configure and send notifications.</td></tr></tbody></table>

### Sending a notification

1. If the button at the top of the Tile does not show the Broadcast Notification item that you intend to use, and the Tile allows a different item to be chosen, click the button and choose another Broadcast Notification from the pop-up, then click the **OK** button.
2. Select the message that you wish to send.

   **Note:** If there is only one message then it will already be selected for you.
3. Click the **Send Notification...** button.

   The system will now look up the relevant Cardholders and load them into a list in a Broadcast Notification Content pop-up.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-e25045dfabb2ad74f9a62bfc38632136fb680cac%2Fbroadcastnotificationsend.png?alt=media)
4. You may now add additional Cardholders to the list of recipients, and also make changes to the message that will be sent. These changes are not saved they only apply to this message being sent.

   **Note:** The **Remove Cardholders** button is enabled when one or more cardholders are selected. Cardholders can be removed by selecting them and clicking the **Remove Cardholders** button.
5. Click the **Send Notification** button.

   The Broadcast Notification Content pop-up closes and the system begins notifying Cardholders.

   The following event is logged:

   *Operator "\<operator name>" initiated a Broadcast Notification "\<broadcast notification list name>"*.

   Further events will be logged, one per email batch, which indicates if the Cardholders were all successfully notified.

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

   **Notes:**

   * You may have to scroll down in the Tile to find the message you are looking for.
   * Upon clicking the **Send Notification...** button on the Tile, the system looks up Cardholders according to the configured criteria. This search may take a moment and will only find Cardholders that the operator sending the broadcast Notification has "View Cardholders" privilege for, so you must ensure that the operator has "View Cardholders" privilege for the divisions required or some Cardholders will not be notified.
   * Cardholders to be notified must have the Notifications checkbox checked for relevant "Email" or "Mobile" Personal Data Fields in order for the Cardholder to receive notifications. If the Notifications checkbox is not checked, the Cardholder will not receive notifications and no error will be reported.


---

# 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/working-with-viewers/tile-actions/broadcast-notification-tile-actions.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.
