Assigning Users and Customizing Notifications
Once you understand the prebuilt notifications in your portal, the next step is assigning the people who should receive alerts. Adding users, contacts, or groups ensures that notifications are delivered to the right individuals at the right time.
This section explains how to assign recipients, how the notification chain works, and which settings you may want to adjust as you begin customizing your alerting experience.
Assigning Users, Contacts, and Groups to a Notification
Every notification includes a notification chain, which defines who receives alerts and by which methods (email, SMS, or phone). Notifications will not send alerts until at least one recipient is added.
To assign recipients:
- Click the gear icon at the top right of the portal.
- Select Notifications.
- Open one of the prebuilt notifications.
- Scroll to the Notification Chain section.
- Add Users, Contacts, or Groups.
- Choose one or more delivery methods for each recipient.
- Click Save.
Why Groups Are Powerful
Adding a group ensures:
Every person assigned to that group will automatically receive the notification.
As your staff changes, group membership can be updated without modifying each notification.
Customizing Notification Settings
Each notification includes several settings that control how alerts behave. Most customers use the recommended defaults, but you can tailor certain options to better match your workflows.
Below are the settings you can modify, along with guidance for when adjustments may be helpful.
Notification Delay
This controls how long the system waits before triggering an alert.
When to adjust:
- Longer delays may help reduce unnecessary alerts during brief temperature fluctuations or slow network moments.
- Shorter delays may be preferred for high-risk environments or critical storage areas.
Acknowledge Requirement
If enabled, users must acknowledge the notification to stop additional alerts.
When to keep ON (recommended):
- Environmental excursions
- Missed check-ins
- Battery-related monitor events
When to turn OFF:
- Nonessential informational alerts that do not require user confirmation.
Resolution Requirement
If enabled, the event must be resolved (with a chosen status) before closing.
Recommended for:
- Temperature excursions
- Humidity excursions
- Any condition requiring corrective action documentation
Not recommended for:
- Monitor messages or simple connectivity warnings
Auto-Close
When enabled, the system automatically closes the event once the condition clears.
Recommended for:
- Missed check-ins
- Minor monitor issues that resolve automatically
Not recommended for:
- Temperature or humidity excursions, which typically require documentation
Notification Snooze
Snooze temporarily pauses alerts for a user after acknowledging an event.
Recommend enabling when:
- Events commonly take time to resolve
- You want to reduce alert fatigue
- Staff may be working on an issue in a controlled timeframe
Not recommended when:
- The condition is unsafe or requires continuous visibility
Repeat Alerts
Repeat settings control whether notifications continue sending until the issue is resolved or acknowledged.
Recommended repeats:
- Excursion Event Notification
- Running on Battery Event Notification
- Missed Check-In Notification
Lower or limited repeats:
- Monitor messages
- Informational or low-impact alerts
Making Thoughtful Adjustments
While the system defaults support most environments, thoughtful adjustments can help tailor notifications to your facility’s workflow—for example:
- Increasing the delay to reduce false alarms
- Enabling snooze for issues that take time to correct
- Increasing repeat frequency for critical conditions
- Turning auto-close on for self-resolving events
These changes help your notification system feel more aligned with the way your team operates.
Next Steps
Now that your notifications have recipients and are properly configured, the next step is learning how events behave once notifications are triggered.
Continue to: