> 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/overall-process-setting-up-notifications.md).

# Overall Process - Setting up Notifications

### Introduction

This section describes the overall process (to be performed by the System Administrator) for configuring Command Centre for Messaging.

Five types of Notifications can be configured in Command Centre:

* Event/Alarm Notifications to specified Cardholders;
* Event/Alarm Notifications to related Cardholders within an Access Group (Personalised Notifications);
* Card and Competency Expiry Notifications;
* Broadcast Notifications; and
* Mobile Notifications for Mobile Client users.

When necessary, this process refers to separate step-by-step procedures that are detailed elsewhere, (i.e. either as separate procedures in this section, or in other sections in this help).

**Note:** To help you understand how the Notifications feature works, and the various components that need configuring depending on what your site wants to achieve, see [Notification Examples](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/notifications/notification-examples.md).

***

### Process

Use the appropriate procedure below for the type of Notification you want to set up:

<details>

<summary>Setup for Event/Alarm Notifications and Personalised Notifications</summary>

1. Set up the Notification, Email, and SMS Server properties.

   Refer to [Notifications](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/notifications.md), [Outgoing Email](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/outgoing-email.md), [Incoming Email](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/incoming-email.md) and [Mobile/SMS Notifications](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/mobile-sms-notifications.md) for the procedures.
2. Configure Notification Filters.

   Notification Filters define the types of events/alarms and the event sources (doors, inputs, etc.) about which a person will be notified.

   Refer to [Creating a Notification Filter](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/notifications/creating-a-notification-filter.md) for the procedure.
3. Create "Email" and "Mobile" type PDFs, assign them to an Access Group, and enter email addresses and mobile phone numbers against all Cardholders/Operators that need to receive email and SMS notification of certain events and/or alarms.

   Refer to [Setting Cardholder "Email" and "Mobile" PDFs](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/notifications/setting-cardholder-quot-email-quot-and-quot-mobile-quot-pdfs.md) for the procedure *.*
4. Enable which Cardholders can be sent messages, and when and how they should be sent.

   Refer to [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) for the procedure.

   **Note:** Continue to Step 5 if you want to set up Personalised Notifications. Otherwise, stop here.
5. Assign Access Groups to Notification Filters (this allows Cardholders in these Access Groups to be sent notifications of events that are related to them).

   Refer to [Creating a Notification Filter](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/notifications/creating-a-notification-filter.md) for the procedure.
6. If you want another person, (e.g. supervisor, administrator) to receive the same notifications as a Cardholder, create a Role and assign both the employee (Cardholder) and the additional person to the Role.

   Refer to [Setting up Roles](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/notifications/setting-up-roles.md) for the procedure.

</details>

<details>

<summary>Setup for Card and Competency Expiry Notifications</summary>

1. Set up the Notification, Email, and SMS Server properties.

   Refer to [Notifications](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/notifications.md), [Outgoing Email](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/outgoing-email.md), [Incoming Email](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/incoming-email.md) and [Mobile/SMS Notifications](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/mobile-sms-notifications.md) for the procedures.
2. Set the Time that the daily Card and Competency Expiry Notification procedure should be run.

   Refer to [Notifications](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/notifications.md) for the procedure.
3. Create "Email" and "Mobile" type PDFs, assign them to an Access Group, and enter email addresses and mobile phone numbers against all Cardholders/Operators that need to receive email and SMS notification of pending Card and Competency expiries.

   Refer to [Setting Cardholder "Email" and "Mobile" PDFs](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/notifications/setting-cardholder-quot-email-quot-and-quot-mobile-quot-pdfs.md) for the procedure *.*
4. Determine Cardholder and Competency expiry threshold values.

   Refer to [Setting Expiry Notification Threshold Values](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/notifications/setting-expiry-notification-threshold-values.md) for the procedure.
5. Create Roles to define relationships between cardholders, (for the purpose of routing notifications), and assign cardholders to the Roles.

   Refer to [Setting up Roles](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/notifications/setting-up-roles.md) for the procedure.

</details>

<details>

<summary>Setup for Broadcast Notifications</summary>

Refer to the topic *"Broadcast Notification Configuration"* in the Command Centre Online Help.

</details>

<details>

<summary>Setup for Mobile Notifications</summary>

1. Enable Mobile Notifications.

   Refer to [Mobile/SMS Notifications](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/mobile-sms-notifications.md) for the procedure.
2. Connect Command Centre to the Cloud.

   Refer to [Connecting to the Cloud](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/services-and-workstations/connecting-to-the-cloud.md) for the procedure.
3. Configure Notification Filters.

   Notification Filters define the alarms that will be sent as Mobile Notifications.

   Refer to [Creating a Notification Filter](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/notifications/creating-a-notification-filter.md) for the procedure.
4. Enable which Mobile Client users can be sent Mobile Notifications, and when they should be sent.

   Refer to [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) for the procedure.

</details>


---

# 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/overall-process-setting-up-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.
