> 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-management/notifications/notification-examples.md).

# Notification Examples

### Introduction

This topic provides three different scenarios, and the configuration required to set up Notifications.

### Example 1

For the Security Manager to receive all Critical alarms 24 hours per day, as well as all Door Open Too Long alarms during working hours only (both via SMS and Email), configure the following:

1. Set up the email server details on the **Outgoing Email** tab of the Server Properties to enable outgoing emails.
2. Set up the SMS details on the **SMS Notifications** tab of the Server Properties to enable outgoing SMS.
3. Create a **Notification Filter** (named something like "Critical Alarms"), and on the **Notifications** tab:
   * set "Include all Events at or above priority:" to Critical Priority
   * ensure the "Include events within all Event Sources" radio button is selected.
4. Create another **Notification Filter** (named something like "Door Open Too Long"), and on the **Notifications** tab:
   * do not set a minimum priority level
   * select the "Door Open Too Long" Event Group/Type.
5. Create a **Notifications Schedule** (named something like "Working Hours Notifications"), and set the Notifications Enabled times between 8:30 a.m. and 5:00 p.m.
6. Open the Security Manager's Cardholder properties, and on the **Event Notifications** tab:

   * drag and drop the two Notification Filters created in Steps 3 and 4.
   * drag and drop the "Working Hours Notifications" schedule (created at Step 5) against the "Door Open Too Long" Notification Filter.

     **Note:** Since the "Critical Alarms" Notification Filter is required 24x7, there is no need to have a schedule associated with it, (i.e. no schedule means the same as "always enabled").
   * ensure the Notification Method is set to "SMS" alongside both of the filters. Repeat the previous two bullet points and ensure the Notification Method is set to "Email" alongside both of the filters.
   * set the **Current Event Notification Status** to ENABLED.

   On the **Personal Data** tab, ensure there is an "Email" PDF and a "Mobile" PDF set up correctly, and that the **Notifications** check boxes are ticked alongside these.

### Example 2

For the HR Manager to receive email expiry warning notifications for all Cardholders that have a card or competency expiry due, configure the following:

1. Set up the email server details on the **Outgoing Email** tab of the Server Properties to enable outgoing emails.
2. For the relevant Card Types and Competencies, on the **Setup** tabs:
   * set the **Advance notice period**, and
   * ensure the related "Enable card/competency expiry notification" check boxes are ticked.
3. Create the "HR Manager" Role, and on the **Notifications** tab enable the Card and Competency Expiry Warnings for this Role.
4. Add the "HR Manager" Role to each Cardholder (on each Cardholder's **Relationship** tab), and populate with the name of the HR Manager.

   **Note:** This can be achieved easily for large numbers of Cardholders using [Cardholder Bulk Change](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/notifications/assigning-cardholders-to-roles-via-bulk-change.md).
5. Open the HR Manager's Cardholder properties, and on the **Personal Data** tab ensure that:
   * there is an "Email" PDF set up correctly, and
   * the **Notifications** check box is ticked.

### Example 3

For John Smith to receive an SMS for his card expiry warning notifications, configure the following:

1. Set up the email server details on the **Outgoing Email** tab of the Server Properties to enable outgoing emails.
2. Set up the SMS details on the **SMS Notifications** tab of the Server Properties to enable outgoing SMS.
3. For the relevant Card Types, on the **Setup** tab:
   * set the **Advance notice period**, and
   * ensure the "Enable card expiry notification" check box is ticked for each card type.
4. Open John Smith's Cardholder properties, and on the **Personal Data** tab ensure that:
   * there is a "Mobile" PDF setup correctly, and
   * the **Notifications** check box is ticked.

### Example 4

For a Cardholder within an Access Group to receive their own Access Denied alarms via email, configure the following.

**Note:** Cardholder records must each have an email PDF set up correctly and the **Notifications** check box must be ticked. You can do this by navigating to **Manage** > **Cardholders** and reviewing the **Personal Data** tab.

1. Set up the email server details on the **Email Notifications** tab of the Server Properties page to enable outgoing emails.
2. Create a Notification Filter called, for example, ‘Access Denied Alarms’.
3. On the **Notifications** tab:
   * Select the 'Access Denied' event group.
   * Ensure the **Include events within all Event Sources** radio button is selected.
4. On the **Personalised Notifications** tab, drag and drop the Access Group into the top grid.

   **Note:** Selecting a schedule for this Access Group is optional; no schedule means the same as ‘always enabled’.
5. Ensure the Access Group's **Notification Method** is set to ‘Email’.

### Example 5

For a supervisor to receive Access Denied alarms via email, configure the following.

**Note:** For every person who you want to receive notifications (whether a supervisor receiving notifications related to their staff, or a Cardholder receiving their own notifications), their Cardholder records must each have an email PDF set up correctly and the **Enable Event Notifications** check box must be checked on their **Event Notifications** tab.

1. Complete Example 4 above.
2. Create a ‘Supervisor’ Role.
3. Open the Properties of the Cardholder to whom you want to add this relationship.
4. Add the 'Supervisor' Role to the **Relationship** tab, and drag and drop the Cardholder who is this Cardholder's supervisor onto the Role in the grid.
5. Drag and drop the 'Supervisor' Role into the bottom grid on the Notification Filter's **Personalised Notifications** tab.
6. Set the **Notification Method** for this Role to 'Email - Separate' or 'Email - CC' as required.


---

# 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-management/notifications/notification-examples.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.
