--- title: Alert Overrides (New) description: BloodCOMM is able to send a wide array of alerts, in a variety of formats. --- [Skip to content](https://info.deltadevteam.com/bloodcomm-alerts-org-overrides#main-content) [Customer Support Portal](https://tickets.deltadevteam.com/portal?hsLang=en) [![DDTResourceCenter](https://info.deltadevteam.com/hs-fs/hubfs/DDTResourceCenter.png?width=204&height=72&name=DDTResourceCenter.png)](https://info.deltadevteam.com/?hsLang=en) - [Hardware Support Ticket](https://info.deltadevteam.com/technical-support-hardware) - [BloodCOMM Support Ticket](https://info.deltadevteam.com/technical-support-software) Open main navigation Close main navigation - [Hardware Support Ticket](https://info.deltadevteam.com/technical-support-hardware) - [BloodCOMM Support Ticket](https://info.deltadevteam.com/technical-support-software) - [Customer Support Portal](https://tickets.deltadevteam.com/portal) - [deltadevteam.com](https://deltadevteam.com/) [deltadevteam.com](https://deltadevteam.com/) Welcome to the DDT Resource Center. Use the search below to find articles, or click on a category. - There are no suggestions because the search field is empty. 1. [Delta Development Resource Center](https://info.deltadevteam.com/?hsLang=en) 2. [BloodCOMM](https://info.deltadevteam.com/bloodcomm?hsLang=en) 3. [Organization](https://info.deltadevteam.com/bloodcomm?hsLang=en#organization) August 12, 2026 # Alert Overrides (New) ## Organizations may override personal alert settings ##### ![](https://info.deltadevteam.com/hs-fs/hubfs/image-png-Aug-04-2026-03-45-57-5358-PM.png?width=670&height=349&name=image-png-Aug-04-2026-03-45-57-5358-PM.png) ##### IMPORTANT: Action Required for Alerts In order to receive organizational alerts, every user in your Organization must properly set up their "Alerting Channels". For example, this means verifying email and phone number, or enabling Push Notifications.   Individual users' verification status is visible on the Users tab.  [Read more](https://info.deltadevteam.com/bloodcomm-alerts-overview?hsLang=en).    **Default Excursion Alerts** All organizations will have Excursion Alerts enabled for all users and all devices by default. This means that every user will receive an alert whenever a device they have access to crosses the 2°C or 6°C threshold. It is **highly recommended** to keep this setting enabled to ensure compliance with AABB requirements. To limit which users receive alerts for specific devices, you should set up your **[organization's](https://info.deltadevteam.com/bloodcomm-teams?hsLang=en)[Team](https://info.deltadevteam.com/bloodcomm-teams?hsLang=en)[s](https://info.deltadevteam.com/bloodcomm-teams?hsLang=en)**.   ##### Configuring Organization Alerts (Admin Guide) As an administrator, you have the ability to set mandatory Organization Alerts. This allows you to push global alert settings down to your users, ensuring that critical notifications—such as a temperature excursion on a blood transport cooler—are received by your team at the exact thresholds you define. Organization alerts cannot be modified or deleted by end users.  Users will receive the specified alerts under the following conditions: - The relevant "Alert Channel" (i.e., SMS or email) has been set up - The user has not disabled "Cloud Alerts" entirely ##### Using the Alert Configuration Wizard Setting up an Organization Alert is very similar to setting up a personal alert. You will use the standard Alert Configuration Wizard, which guides you through selecting the **Alert Type** (e.g., Device Temperature, Time Until Excursion), **Device Subscription**, **Thresholds**, and **Notification Channels**. - **For a general overview of how alerts work:** [Read the Alerts Overview](https://info.deltadevteam.com/bloodcomm-alerts-overview?hsLang=en) - **For standard wizard step-by-step instructions:** [Read the Alert Configuration Guide](https://info.deltadevteam.com/bloodcomm-alert-configuration?hsLang=en) ##### The Key Difference: User Assignment Because you are configuring an alert on behalf of others, the Organization Alert wizard includes one unique step not found in personal settings: **User Assignment**. During this step, you will choose exactly who receives this mandatory alert: - **All Users:** The alert will be assigned to every user in your organization. - **Specific Teams:** The alert will only be assigned to users within the specific Team(s) you select. **Important Note on Team and Device Routing:** When you configure an Organization Alert for a specific Team, BloodCOMM uses intelligent routing to prevent alert fatigue. The alert will *only* trigger for the intersection of users and devices on that shared team. > If you set the User Assignment to "Station 4 Team" and the Device Subscription to "All Devices", BloodCOMM will only alert the users on the Station 4 Team when a device *also* assigned to the Station 4 Team triggers the threshold. They will not receive alerts for Station 5's devices. ##### Summary and Review At the end of the wizard, a summary will display all selected settings for your review. If you are updating an existing Organization Alert, the summary will highlight the exact differences between the old and new settings before you save. - [APRU 6L](https://info.deltadevteam.com/apru-6l?hsLang=en) - [ICE 2L](https://info.deltadevteam.com/ice-2l?hsLang=en) - [BloodCOMM](https://info.deltadevteam.com/bloodcomm?hsLang=en#main-content) - [Overview](https://info.deltadevteam.com/bloodcomm?hsLang=en#overview) - [Bluetooth connectivity](https://info.deltadevteam.com/bloodcomm?hsLang=en#bluetooth-connectivity) - [Organization](https://info.deltadevteam.com/bloodcomm?hsLang=en#organization) - [Device Dashboard](https://info.deltadevteam.com/bloodcomm?hsLang=en#device-dashboard) - [Device Reports](https://info.deltadevteam.com/bloodcomm?hsLang=en#device-reports) - [Blood Dashboard](https://info.deltadevteam.com/bloodcomm?hsLang=en#blood-dashboard) - [Cold Chain Events](https://info.deltadevteam.com/bloodcomm?hsLang=en#cold-chain-events) - [Blood Reports](https://info.deltadevteam.com/bloodcomm?hsLang=en#blood-reports) - [GPS Dashboard](https://info.deltadevteam.com/bloodcomm?hsLang=en#gps-dashboard) - [Metrics Dashboard](https://info.deltadevteam.com/bloodcomm?hsLang=en#metrics-dashboard) - [User Preferences](https://info.deltadevteam.com/bloodcomm?hsLang=en#user-preferences) - [Alerts](https://info.deltadevteam.com/bloodcomm?hsLang=en#alerts) - [Device Manager](https://info.deltadevteam.com/bloodcomm?hsLang=en#device-manager) - [Subscriptions](https://info.deltadevteam.com/bloodcomm?hsLang=en#subscriptions) - [Integrations](https://info.deltadevteam.com/bloodcomm?hsLang=en#integrations) - [Legal](https://info.deltadevteam.com/bloodcomm?hsLang=en#legal) - [API Reference](https://info.deltadevteam.com/bloodcomm?hsLang=en#api-reference) - [Cybersecurity & Trust](https://info.deltadevteam.com/cybersecurity-trust?hsLang=en) - [Procurement & Pricing](https://info.deltadevteam.com/procurement-pricing?hsLang=en) - [Support & Service](https://info.deltadevteam.com/support-service?hsLang=en) [![DDT\_Logo\_White](https://info.deltadevteam.com/hs-fs/hubfs/DDT_Logo_White.png?width=194&height=56&name=DDT_Logo_White.png "DDT_Logo_White")](https://info.deltadevteam.com/?hsLang=en) [Contact Us](https://deltadevteam.com/contact-us) Copyright © 2026, Delta Development Team, Inc. [Privacy Policy](https://deltadevteam.com/privacy-policy/)