Creating or Cloning Notifications (Advanced Use)
Most facilities use the prebuilt notifications included with Stat Temp, but there are times when you may want to create a customized notification for a specific workflow, department, or alerting need. Custom notifications allow you to tailor how alerts behave, who receives them, and which event types they monitor.
This section explains when to create a new notification, when cloning is the better option, and how to configure the notification’s settings before assigning it to devices.
When You Should Create a New Notification
Creating a new notification is helpful when:
- A department or group needs a unique set of recipients
- You want different behavior than the prebuilt notification provides
- You need separate notifications for different storage zones
- You want different repeat behavior or acknowledgement settings for certain teams
- Your workflows require specific escalation or scheduling rules
If your facility has different alerting expectations across locations or staff roles, custom notifications can help you route alerts more appropriately.
When Cloning Is the Better Choice
Cloning copies an existing notification—including its behavior settings—and creates a duplicate that you can rename and adjust. Cloning is ideal when:
- You want to reuse a notification with a different group of users
- You like an existing notification’s settings, but need variations
- You want to create consistency across multiple departments
- You’re building out a group-based alerting strategy
Most organizations clone far more often than they create from scratch.
It saves time and helps maintain consistency across your system.
How to Create a Notification
-
Click the gear icon in the top-right corner of the portal.
Select Notifications.
Click Create a Notification.
Enter a name that clearly identifies the notification’s purpose.
-
Examples: “Pharmacy Critical Temp,” “Lab Missed Check-In,” “Warning Temp – OR”
Select the device type (Sensor or Monitor).
- This cannot be changed later.
-
- Configure behavior settings (delay, acknowledgment, resolution, repeat, etc.).
- Add users, contacts, or groups (optional at this stage but recommended).
- Click Save.
Your notification is now ready to be assigned to sensors or monitors in Section 5.
How to Clone an Existing Notification
- Click the gear icon in the top-right corner of the portal.
- Select Notifications.
- Find the notification you want to reuse.
- Click the three-dot menu next to it.
- Select Clone.
- Rename the newly created notification.
- Adjust event settings, recipients, or behavior as needed.
- Click Save.
Cloning is especially useful when different departments have similar but slightly different needs.
Choosing a Name That Works
Notifications appear throughout your portal, so a clear naming strategy helps keep them organized.
Recommended naming patterns:
| Purpose | Example |
|---|---|
| Department-specific alerts | Pharmacy – Critical Temp |
| Workflow-specific alerts | Lab – Missed Check-In |
| Warning-level alerts | Freezer 12 – Warning Temp |
| Shift or team alerts | Facilities On-Call – Power/Battery |
Avoid overly general names like “Notification 1” or “Sensor Alert,” which make assignments harder later.
Configurable Notification Settings
Each notification includes behavior settings that determine how alerts are delivered. The table below summarizes what each setting does and when you may want to adjust it.
| Setting | What It Does | When to Use |
|---|---|---|
| Notification Delay | Sets how long Stat Temp waits before triggering an alert. | Choose a delay that reflects how quickly you need to know about a condition. Short delays provide faster alerts; longer delays help filter out brief, harmless fluctuations. |
| Acknowledgment Required | Requires a user to manually acknowledge the alert. | Use when staff must confirm awareness of an issue. Acknowledging also stops further notifications. |
| Resolution Required | Requires a user to record how the issue was resolved. | Use when documentation is important for compliance, audits, or internal tracking—especially for environmental excursions. |
| Auto-Close | Automatically closes the event when the condition returns to normal. | Use when the condition typically resolves on its own, such as missed check-ins or signal-related events |
| Snooze | Pauses notifications temporarily after acknowledgment. | Use when resolving the issue takes time and continued alerts would be distracting. |
| Repeat Behavior | Determines whether notifications resend until addressed. | Use repeats for critical issues that require immediate attention or confirmation, such as excursions, communication loss, or battery issues. |
Next Steps
Now that you can create or clone notifications, the next step is connecting them to your devices:
→ Assigning Notifications to Sensors and Monitors
This ensures your notifications are active and monitoring the correct conditions.