Private alerts and escalations
January 6, 2026
We know that some alerts and escalations can contain sensitive information that should only be viewed by certain individuals within your organization (e.g. the Security team). Now, you can leverage private alerts and escalations to restrict visibility to specific teams and individuals.
Up until recently we only supported private incidents. Now, you can create private alerts, which keep any resulting escalations or incidents private as well. Everything can remain be private end-to-end.
You can get started on setting these up by creating a new alert source and enabling the "Private" toggle at the bottom of its configuration screen. If you’d like to learn more about private alerts and how to set this up, please view our help article for more details!
Refreshed escalation path editor
We've made a few tweaks to our escalation path editing experience to make it feel just a bit nicer, including:
- When you load an escalation path we'll default zoom the screen to fit it all in one view
- When you add a new level to the escalation path, we'll let you choose the type (Notify, Slack message, Condition, Repeat); Previously you had to add a Notify node and then know to click the overflow menu to convert it
- Conditions now have numbers, so when you say
Repeat from Condition 1, it's clear whatCondition 1actually is - Shrunk the sidebar so there's a little more space for configuring your escalation path
- Tidied up the Slack message nodes so they look a little cleaner
What else we’ve shipped
New
- We now support getting the current users on-call tied to an escalation path via API
- We automatically set the incident lead as the host of the associated Zoom call
Improvements
- We've made some under the hood improvements to list views on mobile, which means they should perform better
- We've made some under the hood improvements to our logging and error reporting on mobile which helps us monitor rollouts and respond to incidents faster
- We've made it clearer from a team catalog entry that escalation paths should be linked from a team's page or an escalation path
- You can now view all the scopes under a permission, even if you don't have the permission itself, which can useful if you want to ask someone to give you a particular scope in a custom role
- We've improved the validation error messaging you receive when editing schedules
- When importing external schedule overrides, we now skip override creation when the user isn't found, instead of assigning to "nobody"
- We've improved the formatting of escalation descriptions on mobile, to make them easier to read
- We've made it easier to distinguish between users with identical names when using the escalate form
- Improved validation when multiple escalations are mapped to a single team
- We won't chase you with notifications for policy violations on test incidents
- When you add or remove attributes on a catalog type, the list of entries will now update when you go back
- We now show an "Escalate" button below the description on incident homepages
- On the team page, if you have no active incidents, the empty state box is now aligned with the 'view mode' buttons to its top right
- When you don't specify any schedules when downloading a pay report, we'll now include all schedules on the report
Bug fixes
- We've fixed an issue where searching for escalation paths wouldn't give you great results if your search term included a space
- We've fixed an issue which prevented forms from being created via "Copy from existing"
- We've fixed inaccurate CSV exports from the Teams page
- Fixed a bug where the wrong rotation was selected when clicking through shifts
- Fixed a bug on the team schedules page where, in some cases, one of the schedules was displayed incorrectly
- We've fixed an issue where filtering escalations by "Acked" status did not return all acknowledged escalations
- We've fixed a bug where holidays from some calendar feed integrations were imported with the incorrect duration onto schedules
- We no longer let you specify a negative grace period for escalations for grouped alerts
- Fixed setting custom fields in incident declare form via URL for multi-select custom fields
- Fixed an issue where we sometimes wouldn't rename an incident Slack channel after renaming the incident
So good, you’ll break things on purpose
Ready for modern incident management? Book a call with one of our experts today.
We’d love to talk to you about
- All-in-one incident management
- Our unmatched speed of deployment
- Why we’re loved by users and easily adopted
- How we work for the whole organization
