Notifications help users stay informed when something important happens to an asset, such as an alarm, a warning, or another event that requires attention. They are used to make sure the right users receive the right information at the right time.
A notification setup is built in layers. At the bottom, incoming asset data is interpreted through event definitions. These events are then used in notification presets, which define how notifications should be sent for a specific asset type. Notification presets are grouped into notification roles, and those roles are finally assigned to users and assets.
How notifications work
The notification flow works as follows:
Event definitions determine when incoming asset data should be treated as an event.
For example, a tank level can be marked as warning or critical when it passes a threshold.Notification presets define which of those events should generate a notification, for which sensors, in which event states, and through which channels.
Notification roles group together one or more notification presets so they can be assigned in a clear and reusable way. These roles are often based on a user profile, such as Customer, Technical Service, Maintenance, or Accounting.
Assigning notifications links a user to an asset or asset group and assigns the appropriate notification role. This determines which notifications that user will actually receive.
In short: data becomes an event, events are used in presets, presets are grouped into roles, and roles are assigned to users.
Why these articles are ordered this way
Although the system is built from event definitions upward, these articles are intentionally ordered from the user’s point of view.
In practice, most customers do not need to create event definitions or notification presets themselves. In many cases, these have already been set up in advance. The same often applies to notification roles. For many users, the only action they need to take is assigning notifications to the correct users and assets.
That is why the articles are ordered as follows:
Assigning notifications
Notification roles
Notification presets
Event definitions
This order helps you start with the part that is most relevant to your daily work. If needed, you can then move to the more advanced layers underneath.
Which article should I read?
The right article depends on what you want to do.
Read Assigning notifications if you want to:
assign notifications to a user
link users to assets or asset groups
change which notification role a user has
stop notifications for a user and asset combination
Read Notification roles if you want to:
create a new notification role
group notification presets into one role
define roles for different user profiles
edit or remove existing roles
Read Notification presets if you want to:
define which events should send notifications
choose how notifications are delivered
configure notification settings per asset type
edit or remove existing presets
Read Event definitions if you want to:
define when incoming data becomes an event
set thresholds and levels such as normal, warning, or critical
customize event behavior for an asset type or a specific asset
temporarily disable or remove event definitions
Typical examples
The examples below can help you decide where to start.
I only want a customer to receive notifications for a specific asset
Start with Assigning notifications.
In this case, the notification role and the underlying setup are often already available. You only need to link the correct user, asset, and role.
I want to create a new role for a specific type of user
Start with Notification roles.
This is useful when different types of users, such as customers or service engineers, should receive different notifications.
I want to change which notifications are sent for a certain asset type
Start with Notification presets.
This is where you configure which events create notifications and how those notifications are delivered.
I want to change when a sensor value becomes a warning or alarm
Start with Event definitions.
This is the lowest layer in the flow and determines when incoming data should be recorded as an event.
Summary
Notifications are configured in layers, but most users only work with the top layers of the setup. The technical foundation starts with event definitions, which are used in notification presets. These presets are grouped into notification roles, and those roles are then assigned to users and assets.
Because most customers mainly need to assign or manage notifications, this documentation starts with the actions that are most relevant in daily use and then gradually moves toward the underlying configuration. This makes it easier to find the right article and understand how each part fits into the larger notification flow.