> 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/configuration-client/site-installation/server-properties/notifications.md).

# Notifications

### Introduction

Completing the details on this tab allows an operator to configure:

* whether or not alarm notification recipients will be informed of acknowledgements;
* the time (each day) that Card and Competency expiry warnings are sent to individuals and people in a role, (e.g. Manager);
* the number of emails sent per batch, when sending a broadcast notification; and
* custom HTML email templates for Event, Expiry and Broadcast notifications:
  * **Event Notifications**

    Cardholders are notified of any event as determined by the operator (e.g. access denied duress, escalated alarm).
  * **Expiry Notifications** (for an Individual or a Role)

    Cardholders are notified of Cardholder and Competency expiries as an Individual or within a Role (as appropriate). These are sent at a pre-determined time each day.
  * **Broadcast Notifications**

    The operator can set up general notifications to send to any number of specified Cardholders, (e.g. to alert them of a fire drill, to remind them to complete a certain action).

    **Note:** Broadcast Notifications can also be set up in Command Centre.

Custom Notifications are configured using HTML text. Default HTML email templates are included in the Configuration Client and are accessible via the **Notifications** tab of the Server Properties window (**File** > **Server Properties**). Users are able to send themselves test emails from this tab to ensure that the email has been configured according to their requirements. For further detail refer to **HTML Help.pdf** located in the `‘Documentation’` folder of the Command Centre installation files.

### Procedure

1. Open the **Command Centre Server Properties** window. [How?](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/opening-the-server-properties-window.md)
2. Click the **Notifications** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-7e23d8791ebd4a295c26598a4c9ba5e966e416e6%2Fnotificationstab.png?alt=media)
3. The **Inform alarm notification recipients of acknowledgments** checkbox is ticked by default.

   Leave this checked if you want this to occur.
4. Set an **Expiry Notification Time** if required, for the daily running of Card and Competency expiry notifications (Default = 7:00am).

   **Note:** A new notification will be sent every day only if there is a change, (e.g. another cardholder is added to the warnings). The Expiry Notification Time only applies to Expiry Notifications, not Event or Broadcast Notifications. Two types of Expiry Notifications can be sent:

   * **Your Security Access Expires**

     Emails for warnings of personal/individual expiries. New entries appear in **bold**.
   * **Security Access Expiry Report**

     Cardholders that are in 'Roles' will be notified of expiries for their staff. New entries appear in **bold**.
5. Open the relevant email template by navigating to `C:\Program Files (x86)\Gallagher\Command Centre\EmailTemplates`

   **Notes:**

   * Templates whose file names begin with "Custom" contain colour formatting and a PDF with the Gallagher logo.
   * We recommend that before importing any templates, you back them up by copying and pasting them to a location of your choosing. This is to prevent users from accidentally editing the default templates, because then in order to revert the templates back to their original versions, you will need to re-install them from the Command Centre installation files.
6. Enter the number number of emails to be batched, when sending a broadcast notification, in the **Batch Size** field.

   The batch size determines the maximum number of email recipients that can be placed in a single email, and the maximum number of recipients that can be listed in the details of a single event (Default = 50).

   **Notes:**

   * Recipients of emails are sent in batches for performance reasons, but are listed in the BCC field of the email so as to not disclose the recipient's address to other recipients.
   * Reduce the batch size if your email server is configured to block messages with 50 or more recipients (due to spam filtering).
   * The maximum batch size is 199.
7. Click **OK** to exit and save your changes.

   Click **Cancel** to exit without saving your changes.

   Click **Apply** to save your changes and stay in this window.


---

# 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/configuration-client/site-installation/server-properties/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.
