Assigning Notifications to sensors and monitors

Once your notifications are configured and your recipients are added, the next step is assigning those notifications to the appropriate devices. Assigning notifications ensures that each sensor and monitor knows which alerts to generate for the conditions it detects.

This section explains how assignment works, how Stat Temp handles default sensor behavior, and how to manage assignments in both individual and group-based environments.


When You Need to Assign Notifications

You will assign or adjust notifications in the following situations:

1. After creating or cloning a notification

New notifications must be assigned to devices before they can generate alerts.

2. When setting up groups

Facilities that use group-based alerting often assign notifications when:

  • New equipment comes online that is assigned to a Group
  • New Groups come online

How to Assign Notifications to Devices

You can assign notifications to individual devices or in bulk. The workflow is the same for both sensors and monitors.

To assign notifications:

  1. Navigate to Sensors or Monitors at the top of the portal.
  2. Select one or more devices using the checkboxes.
  3. A blue action bar appears — click Edit Selected.
  4. In the side panel, find the Notifications section.
  5. Select or change the notification assigned to each event type.
  6. Click Save to apply your changes.

Assignments take effect immediately.


Understanding Device Assignment Behavior

Notification assignment behaves differently for sensors and monitors. Understanding these differences helps prevent confusion later.

Sensor Assignments

When a sensor first comes online, it is automatically assigned:

  • Excursion Event Notification for Critical Temperature and Critical Humidity
  • Missed Check-In Notification for communication failures

These defaults are applied unless you have customized your System Default Notifications.

You may need to assign or modify notifications when:

  • Enabling Warning Temperature/Humidity events
  • Creating department-specific or zone-specific notification structures
  • Using cloned notifications for specialized workflows
  • Setting up areas requiring different alert behaviors

Sensors only support one notification per event type, so choosing the correct notification is important.


Monitor Assignments

Monitor notifications are not assigned automatically.

You choose which notifications to apply to each monitor when setting it up.

Stat Temp Recommended Monitor Assignments

Event Type Recommended Notification
Running on Power Monitor Message Notification
Running on Battery Running on Battery Event Notification
Low Battery Running on Battery Event Notification
All Other Monitor Events Optional, based on workflow

These recommendations help ensure that battery-related issues receive clear, actionable alerts while nonessential updates remain informational.

You may need to assign or modify monitor notifications when:

  • Setting up new monitors
  • Changing how teams want to receive monitor-level alerts
  • Applying escalation or conditional schedules
  • Adjusting configurations for facilities with frequent power fluctuations

Assigning Notifications in Group-Based Organizations

Many facilities organize alerts by groups rather than by individual device managers. In these environments, assignment strategies tend to follow one of two patterns:

1. Assign the same notification to many devices

Example:

All pharmacy refrigerators use a single “Pharmacy Critical Temp” notification.

2. Assign different notifications based on responsibility

Example:

  • Lab notifications go to the Lab group
  • OR notifications go to the OR group
  • Nutrition storage uses a “Dietary Services” notification

Best practice for group-based orgs:

Use group-named notifications and assign them to all devices belonging to that department or workflow.

This makes ongoing maintenance easier and reduces errors when staff change roles.


Reassigning Notifications

You may reassign notifications at any time.

Common reasons include:

  • Updating recipients
  • Creating more specialized notifications
  • Changing event type coverage
  • Replacing older notifications that no longer meet workflow needs
  • Consolidating or simplifying multiple similar notifications

Reassignment does not remove historical events; it affects only future alerting behavior.


Next Steps

Now that your notifications are assigned to the correct devices, you’re ready to explore advanced delivery features:

→ Escalation & Conditional (Scheduled) Alerting

These features allow you to route alerts based on time, workflow, or escalation rules.

Still need help? Contact Us Contact Us