> 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/creating-a-notification-filter.md).

# Creating a Notification Filter

### Introduction

A Notification Filter is a set of criteria determining which events and alarms should be notified to Cardholders. There are two ways of assigning a Notification filter to a Cardholder:

1. Assigning the Notification Filter to the Cardholder on the Cardholder's **Event Notifications** tab. This means the Cardholder will be notified about any matching events relating to any Cardholder. See [Enabling Event/Alarm Notifications for a Cardholder](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/notifications/enabling-event-alarm-notifications-for-a-cardholder.md).
2. Assigning an Access Group that the Cardholder is in to Notification Filter on the Notification Filter's **Personalised Notifications** tab (explained later in this topic). This means that only the Cardholder (if within that group) for whom the event was about will be notified.

   **Note:** Roles also allow for notification of someone else linked to the person being notified in either case 1 or 2.

This procedure describes how to create a Notification Filter.

Notification Filters are normally configured against Cardholder records, and send event notifications to those Cardholders (e.g. Guards). Personalised Notifications are configured by assigning Access Groups to the Notification Filter, and send Cardholder-related events only to the related Cardholder if that Cardholder is a member of one of the assigned Access Groups (or a child Access Group).

<table><thead><tr><th width="301">To send event email or SMS to...</th><th>assign...</th></tr></thead><tbody><tr><td>Guards (or non-related Cardholders),</td><td>a Notification Filter to each particular Guard's/Cardholder's <strong>Event Notifications</strong> tab.</td></tr><tr><td>event-related Cardholders,</td><td>to a Notification Filter the Access Group(s) containing the Cardholders to receive event notifications about themselves.</td></tr><tr><td>event-related Cardholders' Relationships (Roles),</td><td>to a Notification Filter the Roles to receive notifications about the Cardholders for whom they are that Role. They only receive notifications about Cardholders who are in the Access Groups assigned to the Notification Filter.</td></tr></tbody></table>

When an Access Group is assigned to a Notification Filter, Cardholders belonging to the Access Group or any of its child Access Groups will receive notifications for events that relate to themselves, as specified by the Notification Filter.

If Cardholders in this Access Group have Roles assigned on their **Relationships** tab, and these Roles are assigned alongside the Access Groups on the Notification Filter's **Personalised Notifications** tab, then event notifications are sent to these Roles.

**Notes:**

* If configuring a Notification Filter for Mobile Notifications, only alarms can be sent, not events. Mobile Notifications will not work when the Notification Filter is assigned to an Access Group. The Notification Filter must be assigned to individual Cardholders.
* Notifications is a licensable feature.

### Operator Privileges

<table><thead><tr><th width="301">To...</th><th>you require the...</th></tr></thead><tbody><tr><td>make a change to a Notification Filter</td><td>"Configure Site" privilege in the appropriate division.</td></tr><tr><td>edit the <strong>Personalised Notifications</strong> tab on a Notification Filter</td><td>"Edit Personalised Notifications" privilege in the appropriate division.</td></tr><tr><td>see/view a Notification Filter</td><td>"View Site" privilege in the appropriate division.</td></tr></tbody></table>

### Procedure

1. Click **Configure** from the menu bar, then **Notification Filters**.

   The **Notification Filter** List Window opens (in [grid view](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/list-windows/grid-view.md)).
2. **Right-click** and select **New\...Notification Filter**.

   By default the **General** tab displays.
3. Complete the fields as required.

   For further detail see [General tab](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/general-tab.md).
4. Click each tab in turn to configure the Notification Filter:

<details>

<summary>Notifications tab</summary>

1. Click the **Notifications** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-f6d49bbba17f0551f909623bc1c2cffa24f4c6e5%2Fnotificationfilter.png?alt=media)
2. To define the Notification Filters, configure as appropriate:

   <table><thead><tr><th width="198">Field</th><th>Description</th></tr></thead><tbody><tr><td>Include:</td><td>Select the required Escalation state from the drop-down list. Options are:<br><strong>Any Escalation State:</strong> Events/alarms that are in any escalation state will be notified.<br><strong>Escalated Events Only:</strong> Only events/alarms that are escalated will be notified.<br><strong>Non-escalated Events Only:</strong> Only non-escalated events/alarms will be notified.</td></tr><tr><td>Include alarm restorals</td><td>Checking this option will send separate notifications for each restoral and reactivation of a stateful alarm.</td></tr><tr><td>Include all events at (or above) priority:</td><td><p>Checking this option:</p><ul><li>enables the drop-down list of priorities, allowing you to select another of the existing priorities, and</li><li>the text below changes from "<strong>Include all</strong> Events of Group/Type" to "<strong>As well as</strong> Events of Group/Type"</li></ul><p><strong>Note:</strong> If you do not check this option, at least one Group or Type must be selected.<br>Default = The second highest Priority level<br>Selecting the <strong>at priority</strong> option only notifies that priority's events, whereas the <strong>at or above priority</strong> option notifies events of that priority and above.</p></td></tr><tr><td>Include all Events of Group/Type:</td><td>If an Event Group is selected then all Event Types belonging to the Event Group will be notified. It is possible to select various Event Types within a particular Event Group.<br>Default = None selected</td></tr><tr><td>Include events within all Event Sources</td><td>If enabled, then you cannot restrict the Event Sources, (i.e. you cannot select specific Event Source items). Notifications are not restricted by event source when this option is selected.<br>Default = Enabled</td></tr><tr><td>Include events from the following Event Sources</td><td>If you check this radio button, then at least one item needs to be dragged and dropped into the Event Sources grid. There is no restriction to the number of Event Sources, (i.e. Divisions, Cardholders, Alarm Zones, Access Zones and Items), that can be included in this grid.<br>Notifications will be restricted only to these event source(s) when this option is selected.<br>Default = Disabled (None included)</td></tr></tbody></table>

</details>

<details>

<summary>Personalised Notifications tab</summary>

1. Click the **Personalised Notifications** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-288ce61133cd1509178e50fb7b2d105d6d48e7b0%2Fnotificationfilter_personalisednotificationstab.png?alt=media)
2. In the top grid, drag and drop the Access Groups whose Cardholders (and Cardholders of child Access Groups) are to receive personal notifications as per the configuration in the **Notifications** tab. The Cardholders in these Access Groups will only receive notifications about events that relate to themselves.

   **Note:** If a Cardholder is in more than one of the Access Groups in this grid, they will still only receive one notification per related event, unless the different Access Groups have different notification methods, in which case they will receive the separate notifications.
3. Optionally assign a schedule to an Access Group by selecting the Access Group then choosing a schedule from the **Optional Schedule** drop-down list.
4. Select the notification method ( **Email** or **SMS** ) for an Access Group by selecting the Access Group then choosing a notification method from the **Notification Method** drop-down list.
5. Enable or disable notifications from this Notification Filter for each Access Group by selecting (to enable) or deselecting (to disable) the checkbox to the left of each Access Group's name.
6. In the bottom grid, drag and drop the Roles that are also to receive notifications as per the configuration in the **Notifications** tab. These Roles will be notified for every notification that is:
   * sent to a Cardholder who they have a relationship with, and
   * sent as a result of this Notification Filter.
7. Select the notification method ( **Email - Separate**, **Email - CC**, or **SMS** ) for a Role by selecting the Role, then choosing a notification method from the **Role Notification Method** drop-down list.

   **Email - Separate** will send a separate email notification to the Role for all notifications that are sent to Cardholders (functionality prior to Command Centre v8.40).

   **Email - CC** will carbon copy (Cc) the Role in all emails sent to Cardholders.

   **SMS** will send a separate SMS to the Role for all notifications that are sent to Cardholders.

   **Note:** For Roles to receive notifications via a certain method, the Cardholder who receives the original notification must be in an Access Group that is configured with that same notification method.

   For example, for a Role to receive a notification via SMS, the notification-related Cardholder must be in an Access Group that that is configured with the SMS Notification Method.

</details>

5. Click the **Custom Fields** tab if you want to add and assign a custom field value to this Notification Filter.

   For further details regarding the **Custom Fields** tab, see [Custom Fields](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/custom-fields.md).
6. Click the **Notes** tab if you want to add a note(s) about this Notification Filter.

   For further details regarding the **Notes** tab, see [Notes](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/notes.md).
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.

### Hints

{% hint style="info" %}
**Deleting Notification Filters**

Refer to [Deleting items](https://help.security.gallagher.com/knowledge-hub/configuration-client/introduction-to-command-centre/knowing-your-way-around/generic-properties-configuration/deleting-items.md) for the procedure on how to delete a Notification Filter.

**Note:** Notification Filters cannot be deleted if they are attached to one or more cardholder records.
{% endhint %}

{% hint style="info" %}
**Escalated Events**

Normally an event that matches the assigned Notification Filters will trigger an email, and when the event escalates, it triggers another email. However, when the Messaging service is under significant strain, the event may be escalated before the first email is sent, which results in only the second email being sent. The details of the second email are almost identical to the first, except that the event will show as being "escalated".
{% endhint %}


---

# 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/creating-a-notification-filter.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.
