Overview
Notification settings in Hi Marley determine how and when users are notified about important events, such as new messages, case assignments, and mentions.
Notifications are organized by notification type, with settings applied per delivery channel (such as Chrome or Email) and controlled by an enforcement level.
This structure allows admins to balance consistency with user flexibility.
Who Has Access
- System Admins control notification availability and enforcement
- End users can manage their own notification preferences when allowed
Where to Find Notifications
Admins can manage notification settings from:
Admin → Notifications
From this page, each notification type can be configured independently.
How Notifications Work
When an event occurs in Hi Marley:
- The Notification Type determines what happened
- The Delivery Channel determines how users are notified
- The Enforcement Level determines whether users can control the setting
This layered approach ensures notifications are both reliable and customizable.
For example, for the New Message notification if the chrome notifications may be set to Required and the email notifications may be set to Optional, this ensures users never miss incoming messages, while still allowing them to manage email volume.
Understanding Notification Hierarchy
1. Notification Types
A Notification Type represents a specific event that can trigger a notification.
Examples include:
- Reassigned to a Case
- Policyholder Opt-in
- Primary Operator Assigned
- New Message
- User mentioned in case note
Each notification type appears as its own row in the Notifications table.
2. Delivery Channels (Within Each Notification Type)
Each notification type can be delivered through one or more channels, such as:
- Chrome (in-app/browser notifications)
Channels are configured independently, meaning a notification can be required via one channel and optional via another.
3. Enforcement Levels (Within Each Channel)
For each delivery channel, admins define an enforcement level that controls user behavior.
The available enforcement levels are:
- Required
Notification is enabled for all users and cannot be turned off. - Optional
Users can choose whether to turn the notification on or off. - Disabled
Notification is turned off and cannot be enabled by users.
These enforcement levels ensure critical notifications are always delivered while giving flexibility for less critical events.
Best Practices
- Set critical, time-sensitive notifications (like New Message) to Required
- Use Optional for informational or secondary notifications
- Review notification settings during onboarding or role changes
- Keep enforcement consistent across teams to avoid confusion