> 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/enabling-event-alarm-notifications-for-a-cardholder.md).

# Enabling Event/Alarm Notifications for a Cardholder

### Introduction

The **Event Notifications** tab on the Cardholder properties page allows a privileged operator to Enable and Disable notifications for a particular Cardholder, either instantly, or at a future time or for a particular period of time.

This page also displays the messaging filters that are active for the Cardholder alongside an optional schedule for each filter, as well as a notification method, (i.e. Email, SMS, or Mobile Notifications).

### Operator Privileges

The "Edit Cardholder Notification" operator privilege is required to:

* enable/disable notifications on the **Event Notifications** tab of the Cardholder record.
* change the preferred notification method at the filter level.

In addition to the "Edit Cardholder Notification" privilege, you may require another privilege depending on what function you want to perform, as follows:

<table><thead><tr><th width="282">To...</th><th>you also require the...</th></tr></thead><tbody><tr><td>add or remove a Notification Filter from the Cardholder</td><td>"View Site" privilege in the Notification Filter's division.</td></tr><tr><td>add or remove a Schedule from the Cardholder's Notifications tab</td><td>"View Schedule" privilege in the Schedule's division.</td></tr><tr><td>see and/or update any other Cardholder tabs other than the <strong>Event Notifications</strong> tab</td><td>appropriate Cardholder privilege, (i.e. "Edit Cardholder", "Delete Cardholder", "View Cardholder" or "Edit Cardholder Notes").</td></tr></tbody></table>

### Procedure

1. Click **Manage** from the menu bar, then **Cardholders**.

   The **Cardholder** 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. Locate, and highlight, the Cardholder to edit.
3. **Right-click** and select **Properties**.
4. Click the **Event Notifications** tab.

   **Note:** The **Current Event Notification Status** only affects event notifications, (i.e. it does not affect expiry notifications). By default, all Cardholders **Current Event Notification Status** will be DISABLED.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-ba73c48b1c89a2b6170a982120f8ae514644eaed%2Feventnotifications.png?alt=media)
5. Select the **Enable Event Notifications** check box.

   **Note:** The status will not change until the **Apply** button is clicked, and the name of the check box changes from **Enable Event Notifications** to **Disable Event Notifications**.

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

   If you require Notifications to be enabled for a specific time, set the **From** and **Until** dates and times.

   **Notes:**

   <table><thead><tr><th width="228">If you...</th><th>when the Apply button is clicked, the Event Notification status...</th></tr></thead><tbody><tr><td>enter a date from the future in the <strong>From</strong> field,</td><td>will remain as DISABLED. It will not change to ENABLED until the date and time indicated in the <strong>From</strong> field.</td></tr><tr><td>do not enter a date in the <strong>From</strong> field,</td><td>will become ENABLED immediately.</td></tr><tr><td>do not enter a date in the <strong>Until</strong> field,</td><td>will become ENABLED indefinitely.</td></tr></tbody></table>
6. Click **Configure** from the menu bar, then **Notification Filters**.

   The **Notification Filter** List Window opens.
7. Select those Notification Filter(s) you want to assign to this Cardholder.

   Drag and drop them into the **Event Notifications** tab.

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

   **Note:** By default, when you drag a Notification Filter into this window, it will not have a Schedule associated with it, and the notification method will be "Email".

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-752c49e3f6a866766b797247f2d8c6a388e01d2d%2Fnotificationfilters.png?alt=media)
8. Close the **Notification Filter** List Window.

   Notification Filters can optionally have a schedule associated. A schedule defines the times when events selected by this filter are notified to the Cardholder.

   **Note:** If a schedule is not assigned to a messaging filter, then that filter will be assumed to be enabled at all times.
9. Do you want to associate a schedule with the Notification Filter(s)?

   If **yes**, go to Step 10.

   If **no**, go to Step 13.
10. Click on the required Notification Filter so it is highlighted.

    The **Optional Schedule** and **Notification Method** fields become enabled.
11. Select an **Optional Schedule** from the drop-down list. Alternatively, drag and drop the schedule from the Schedule List Window.

    **Note:** The drop-down list contains only "Notification" type schedules.
12. Repeat Steps 11-12 for any other Filters you want to associate a Schedule with.

    **Note:** A Filter's or Schedule's property page can be opened from this window, by either:

    * double-clicking on the Filter or Schedule in the grid, or
    * right-clicking on the Filter. A context-menu displays, with the option to select either **Filter Properties** or **Schedule Properties**.

      **Note:** If the Filter does not have a Schedule associated with it, the **Schedule Properties** option will be disabled.
13. If you want to change the notification method from "Email", select another option from the **Notification Method** drop-down list.

    See [Mobile/SMS Notifications](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/mobile-sms-notifications.md) for further detail.

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

    **Note:** If configuring Mobile Notifications, select **Mobile Notifications** from the **Notification Method** drop-down list.
14. By default, the ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-78b6786245dd04fd957b81f18dc7f94a341bcae6%2Ftickbox.png?alt=media) check boxes beside each Notification Filter indicates that they are selected to activate the filter.

    If you want to deactivate a filter, deselect the check box beside the relevant filter. Events selected by this filter will no longer be notified to the Cardholder.
15. 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.

### Hint

{% hint style="info" %}
**My Notifications**

The logged-in operator can quickly access the **Event Notifications** tab of their own Cardholder properties (via **Manage** > **My Notifications** ), primarily for the purpose of quick enablement/disablement of event notifications.
{% 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/enabling-event-alarm-notifications-for-a-cardholder.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.
