Using Groups for Large Organizations
This guide is designed to help Stat Temp administrators scale the platform across large organizations with multiple departments, locations, or divisions. It covers how to set up groups, configure users, and establish a consistent approach that ensures clean data segmentation, reliable notifications, and minimal rework.
This guide applies whether you're launching a new Stat Temp site or expanding an existing one.
Key Architectural Concepts
Tenant / Organization (Global Scope)
Each Stat Temp site is a single, standalone tenant—also referred to as the organization. All global settings and system-wide behaviors are controlled at this level.
Global Components include:
- System Settings
- User Roles
- Environment Policies
- Notifications
- Reports
Temperature Units (°F vs °C) are set globally and cannot be mixed within the same tenant. If both units are required, separate Stat Temp tenants must be used.
Groups (Segmentation Layer)
Groups allow administrators to partition data access and system behavior within a single tenant. They are essential for supporting multiple locations or departments under a unified system.
- A user assigned to a group will only see the sensors, monitors, and events for that group, provided their role does not have the “View All” permission.
- When creating a group, administrators assign:
- Existing sensors
- Users (any role)
- Contacts (for notification routing)
- After the group is created:
- New users can be invited directly into the group
- New contacts can be assigned to the group at creation or later
- New sensors can be configured and added to the group as they come online
- Monitors and events are not directly assigned to groups. They inherit group visibility via the sensors they are linked to.
User Roles and Permissions
All users are assigned a global role, which defines their capabilities across the tenant. Understanding role behavior is essential for effective group setup.
Role | Can Be Given “View All”? | Description |
---|---|---|
Administrator | Always enabled | Full access to all data, settings, groups |
Power User | Yes (optional) | Site-level manager; cannot access system settings or roles |
User | Yes (optional) | Standard user; can interact with notifications and reports |
Facilities | Yes (optional) | Read-only visibility; no interaction |
Custom Roles | Yes (optional) | Flexible control; permissions defined by Admins |
Scaling the System
Once a site is established, follow this process every time you need to add a new location, department, or role-based group.
1. Creating Groups
Administrators can create as many groups as needed. Groups can remain empty until sensors are added or users are invited.
Steps to Create a Group:
- Click the gear shift icon on the top right.
- Click Groups
- Select Create Group
- Complete the following:
- Name the group using a consistent format (e.g., “East Pharmacy”)
- Assign sensors that belong to the group
- Add users and contacts
- Click Save
2. Creating Group-Based Notifications
Each group should have its own dedicated set of notifications to ensure alerts are routed only to the appropriate users and contacts. Notifications for groups can be created at any time, even before sensors, monitors, users, or contacts have been added to the group.
For consistency, clone the platform's default notifications, which are pre-configured to meet industry-standard alerting logic.
Why use Groups in Notifications?
- Ensures new users or contacts added to the group are automatically included in alert routing.
- Reduces the need to manually update notifications as staffing changes.
Steps to Create or Clone a Group-Based Notification
- Click the gear icon in the top-right corner
- Select Notifications
- Create or Clone a Notification
- Use Clone if there’s an existing notification with the correct settings (e.g., a critical temperature alert used by another group)
- Or click Create Notification to build one from scratch
- Scroll to the Notification Chain Section
- Assign Groups to the Notification Chain
- Use the dropdowns under each contact method (Email, Text, Phone)
- Select the appropriate Group for each method
- Optionally, add individual users or contacts as needed
- Save the Notification
Repeat this process for each type of notification required
(e.g., Critical Excursion, Missed Check-In, or Monitor Power Events)
3. Assigning Group-based Notifications
Once group-specific notifications are created, they must be assigned to the appropriate sensors and monitors. Without this step, notifications will not activate even if the event conditions are met.
Assigning Notifications to Sensors
- Click Sensors at the top of the Stat Temp website
- Select the sensor you want to configure.
- Scroll to the Notification Settings Section
- Use the dropdown menu next to each notification type to select the notification created for that sensor’s group.
- Save the sensor Configuration
Assigning Notifications to Monitors
- Click Monitors at the top of the Stat Temp website
- Select the monitor you want to configure.
- Scroll to the Notification Settings Section
- Recommended Notifications to configure are:
- Monitor running on external power
- For this notification, you can only assign message-type notifications
- Monitor running on battery
- Running on low battery
- Monitor running on external power
- Recommended Notifications to configure are:
- Use the dropdown menu next to each notification type to select the notification created for that sensor’s group.
- Save the monitor Configuration
4. Inviting Users to Groups
To give users access to group-specific sensors, monitors, and events, they must be invited to the tenant and assigned to the correct group(s).
To invite new Users:
- Click the gear shift icon at the top right of the Stat Temp website.
- Click Invitations.
- Enter the user’s email address.
- Select their user role (Power User, User, Facilities, or Custom).
- Select the group(s) the user should belong to.
- Click Send Invitation to complete the process.
The user will receive an email from no-reply@stattemp.io
with instructions to activate their account. If they do not see it, have them check their junk/spam folder.