Learn how to send unified service-based and high-attention notifications to keep users informed and improve productivity.
Bridge Notification Service Learn how to send unified service-based and high-attention notifications to keep users informed and improve productivity. Bridge Notification Service offers numerous benefits that enhance user experience, improve communication, and boost overall productivity by helping users stay informed about important events.
The Notification service enables platform services to send unified notifications to end users. Notification benefits The Bridge Notification Service enhances communication and overall platform usability by providing the following benefits:
Enhanced user engagement
Real-time communication
Improved user experience
Increased productivity
Reduced email overload
Cost-effective communication
Notification roles and permissions
The following are the roles and permissions for accessing and managing notifications, including the ability to view, create, edit, enable or disable notifications:
Platform Admin, Platform Operator and Platform Editor:
Have full access to notification capabilities. Can create, edit, delete,enable, disable and manage notifications, configure recipients and control notification settings across the platform.
Platform Viewer:
Has view-only access (end-user experience). Can access and read relevant notifications, including acknowledging Priority notifications, and view both notification settings and actual notifications, but cannot make any changes.
Notification types
Notifications are intended for all users within an account and are typically used to communicate important updates, such as scheduled maintenance or planned downtime. They require users to acknowledge receipts, ensuring visibility and awareness of critical information. The following notification types are supported:
Priority notifications:
Priority Notifications: notifications are must-read messages that require users to acknowledge them.
Service-based notifications:
Service-based notifications are automatically generated notifications triggered by system events within Bridge services, providing real-time updates on workflows, operations and system activities. These notifications can be viewed through the notification bell icon or the notification details page, where users can access the full list of notifications.
Supported notification channels
Service notifications are delivered through the following supported channels, allowing users to stay informed based on their preferences and context:
In-app notifications
: In-app notifications are displayed directly within the platform to ensure timely visibility. Users can access them through the notification bell icon or from the notification’s details page.
Email
: Provide an alternative channel for receiving updates outside of the platform. These notifications ensure that users are informed even when they are not actively using the applications. Email notifications are delivered in outlook with configurable headers, content and recipient lists.
Both in-app and email notifications (default selection)
: Enables both in-app and email notifications, allowing users to receive updates directly within the platform as well as via email. This option is selected by default to ensure users stay informed in real time, regardless of where they are.
Notification recipients
Notifications can be targeted at different audiences depending on the intended scope and purpose, typically falling into the following categories:
User notifications:
User notifications are sent to specific individuals or Access Groups within an account. Administrators can assign recipients directly, ensuring that only the intended users receive the notification. When created, user-level notifications remain in Draft status until individual users or Access Groups are added through the UI.
Account-level notifications:
Account-level notifications are broadcast to all users within a selected account. When configured, no individual user selection is required, as notifications are automatically delivered to all users within the defined scope. The account name is applied based on the selected context. Once created and saved, account-level notifications are active by default.