In FDD, a policy defines how event notifications are delivered. A policy determines who receives notifications, how they are notified, what information is included in the notification, and whether escalation rules are applied.

To access Notification Policies, navigate to the FDD module from either the Portfolio View or the Building View, then open the Policies sub-section.

• In Portfolio View, you can see all portfolio-level configurations, as well as policies across all buildings. 

• In Building View, you can see policies specific to that building, along with any portfolio-level policies. Policies from other buildings are not displayed. 

Creating a Notification Policy

To create a policy:

1. Open the FDD module.

2. Navigate to Policies.

3. Click Create Policy.

Enter a Name and Description for the policy. It is recommended to use names that reflect the responsible team or purpose, such as Engineering Team, Security Team, or Energy Management Team.

Configuring Notification Content

Notification content can be customized separately for when an event is created and when it returns to a normal state. 

​

“On Create” Notifications

The On Create settings control the content and behavior of notifications when an event is first triggered, including:

• Auto Close After - Automatically closes an event after it has remained active for a specified period.

• Delivery Methods (Email / Push / SMS): Click the dropdown arrows next to Email, Push, or SMS to expand and configure the message templates for each channel
  

​

“Return to Normal” Notifications 

Return to Normal notifications control the content and behavior of notifications when the event is no longer in alarm and returns to a normal state.

These notifications are disabled by default. To enable and customize them, toggle on the Return to Normal switch on the right side. Once enabled, you can configure the notification settings as needed. 

Similarly to On Create notifications, Return to Normal notifications also include custom configurations for Email, SMS, and Push notifications.

Customizing Alert Content

To insert dynamic event details into your notifications, click inside the Subject or Body text areas where you want the information to appear, and then click the desired field buttons below to add them to your template.

Available fields for notification details include: Building, Device Name, Event Description, Event Name, Event Note, Floor, Point Name, Point Value, Routine Name, and many additional event attributes.

Select the fields that are most relevant to your users.

Assigning Users to a Notification Policy

Users must be included in a notification policy in order to receive and acknowledge notifications generated by that policy.

Once assigned, users will receive notifications according to the policy rules and will be able to acknowledge events associated with that policy, provided they also have the required role permissions.

​

How to Assign Users

To assign users to a notification policy:

1. Open the FDD module and navigate to Policies

2. Open the desired policy

3. Go to the Notify page

4. Add the required users or roles under either:

• Group Configuration

• Custom Configuration

5. Select the desired notification channels

6. Save the policy

Notification Configuration Methods

The platform supports two primary methods for routing notifications: Group Configuration and Custom Configuration.

Group Configuration

Group Configuration is best suited for bulk assignments where multiple users should receive the same type of alert.

With this method, you can:

• Select one or more Roles (e.g., Engineering, Engineering Manager)

• Add Specific Users to the same group

• Choose the same notification channels for all recipients (roles + specific users):

• Email

• Push Notifications

• SMS

• Call

All selected users and roles will receive identical notification types.

​

Custom Configuration

Custom Configuration provides more granular, user-level control over notifications.

Using this method, you can:

• Add individual users or roles using + Add User or + Add Role

• Configure notification methods separately for each entry

For example:

• Engineering role receives only Email notifications

• Engineering Manager receives Email and SMS alerts

• Specific user receives Push and Email notifications

This allows highly tailored notification delivery based on responsibility or urgency.

Configuring Escalations

Escalations ensure that critical events are not missed. If an event remains active and unacknowledged for a defined period, the system automatically escalates the notification to the next level.

Duration in Minutes

Each escalation level requires a time threshold in minutes. This defines how long an event must remain:

• Active

• Unacknowledged

before the escalation is triggered.

Recipient Configuration

Each escalation level supports both Group Configuration and Custom Configuration, similar to the initial notification setup.

This allows flexible routing such as:

• Initial alerts sent to specific individuals (Custom Configuration)

• Escalations sent to entire teams or departments (Group Configuration)

Multiple Escalation Tiers

You can create multiple escalation levels by selecting + Add, allowing notifications to progress through a defined sequence (e.g., 1st Escalation, 2nd Escalation).

This ensures unresolved events are progressively escalated to higher levels of responsibility or additional teams based on priority and duration.

Acknowledging an FDD Event

To acknowledge an event, the following conditions must be met:

• User is assigned to the Notification Policy

• User is assigned to the relevant Building

• The user's role  must have the acknowledgment permission enabled via Launchpad.

Without this role-level permission, the acknowledge action will not be available, even if the user is correctly included in the policy.

Once these conditions are met, users can acknowledge FDD events from the event view or directly through notifications.

This ensures that event acknowledgment is limited to properly authorized users for each site.