> 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/cardholder-viewer/sending-a-notification-from-the-cardholder-viewer.md).

# Sending a Notification from the Cardholder Viewer

An operator with the 'Send Broadcast Notification' privilege can send a notification to one or more Cardholders from the Cardholder Viewer, as follows:

**Note:** Broadcast Notifications is a licensable feature, therefore this option will only appear if your site is licensed for Broadcast Notifications.

1. Click the **Cardholder Viewer** button on the Command Centre toolbar.

   The Cardholder Viewer opens.
2. Select one or more Cardholder records in the Navigation Panel.

   **Note:** The Cardholder to be notified must have the Notifications checkbox checked for the 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.
3. Click the **Actions** button.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-fdaa06d9f9f80d95be6245a8a5e1fe3b27fb7eb8%2Fchold_actionsdropdown.png?alt=media)
4. Select **Send Notification** from the drop-down.

   The Broadcast Notification Content pop-up displays.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-2e90a98d5a3bfcd120c0c584de23ccdda8d9169b%2Fbroadcastnotificationsad-hoc.png?alt=media)
5. If required, click the **Add Cardholders** button to add additional Cardholders to the list of recipients.

   **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.
6. In the right-hand side of the pop-up, choose the type of notification you wish to send, (i.e. either Email, SMS, or both).
7. Enter the message you wish to send.

   **Notes:**

   * If you have selected Email, the grey text above the message will show how many characters have been used, out of the maximum 1000 possible characters.
   * If you have selected SMS, the grey text above the message will show how many characters are left in the current message, followed by a slash, followed by the number of text messages required for sending this message. If the number after the slash is 2 or more, then a multi-part message will be used when sending the message. Check with your email-to-SMS provider to see if they support sending multi-part messages, and what limits the provider has on these.
   * If there is a spelling error in the message, then a red squiggle will appear below the miss-spelt word. Clicking on the squiggle will reveal a list of possible corrections. If the word is in fact correct then the squiggles may be ignored.
8. Click the **Send Notification** button.

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


---

# 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/cardholder-viewer/sending-a-notification-from-the-cardholder-viewer.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.
