Team permissions for alert sources and routes

Late last year, we built out the foundations for team-level permissions, starting out with support for schedules and escalation paths. We’ve now extended these permissions for alert routes and sources which can ensure that teams are not editing or messing with configuration that is owned by another team in your organization.

You can be quite flexible on how you want to apply these permissions too. For example, you can limit editing an alert source to a specific team, but allow any subsequent alert routes to be adjusted by multiple teams.

Check out our help document for more details!

Scribe for Microsoft Teams

We now support Scribe for Microsoft Teams online meetings. This means that organizations who have their incident calls in Microsoft Teams get all the yummy benefits of Scribe - call transcripts, AI generated summaries, and call "key moments" posted regularly into the incident channel.

Please review our helpful Loom to help get started!

Easy migrations to the new post-mortem in-app editor

You can now migrate post-mortems created using our old in-app editor to the new experience yourself. This enables your organization to get access to features such as the new post-mortem list.

Legacy in-app post-mortems that have not been migrated by the end of January will automatically be migrated for you when we sunset the legacy in-app editor, but this gives you the opportunity to try it out earlier if you wish!

Easier chat access in the dashboard

We’ve made it easier to find and chat with incident in the dashboard. Simply click on the alarmalade (orange) button to chat - the button now floats, is resizable, draggable and pinnable!

The chat functionality is currently only available on incident pages, but it will make it even easier for you to ask incident for help during and after your incidents.

Workflows are now a platform feature

Until recently, workflows were only available to customers paying for our Response product. We've now made them available as a platform-wide feature. This means we have three buckets of workflows, including those available to:

Any customer
- Generic workflows such as sending a message via Slack, Microsoft Teams or email
Response customers
- Workflows such as responding to incident events and managing follow-ups
On-call customers
- Workflows to notify about shift changes or escalating via incident.io

What else we’ve shipped

New

We now have a global option in the Slack channel or Teams channel section of Settings that can globally skip automatic channel creation for incidents regardless of incident type
We now automatically invite people to the incident channel when incidents are created from unrelated alerts
Added option to auto delete Scribe call notes after 14 or 90 days
We’ve added a shortcut to Settings in the side navigation bar
Audit logs now include changes to alert priority

Improvements

Refocused our landing pages for On-call only customers to highlight alerts versus incidents
Updated the On-call cards within the dashboard to be clearer and more useful
Improved the error messaging when there are multiple users assigned to a role via the incident creation API
Timeline entries and activity log items now indicate the stream that they occurred in
When 2 or more users with the same name are shown in drop0downs, the user's email address will be displayed
Improved the way nouns are pluralized when editing expressions
Scribe should produce fewer "Key moment" updates when discussion of an existing key moment is ongoing
When connecting an alert source to an alert route, you can now search for the correct alert route
We've added some improved validation errors for the timestamps you set when creating a schedule via the API
We've made the alerts page significantly faster to load
You can now add links to your alert descriptions and incident summaries in alert sources and routes
We've fixed a bug where you'd receive an error if you managed to double-accept a cover request
We've updated the copy around the private incident setting, to make it clearer that this only pertains to manually created things, you can still have private alert sources and routes whilst this toggle is disabled
We've improved the error messaging around requesting cover via the dashboard if you try to request cover for a time period that you're not on-call for
We'll now send you a push notification if someone had previously offered you cover, but has had to withdraw their offer
We now format Javascript expressions using Heredoc when exporting to Terraform, which makes multiline expressions much easier to read

Bug fixes

Fixed a bug where links in follow-up insights would navigate to non-existent incident tabs
Fixed a bug where the teams setting configuration tab would be hidden if no teams had members
Fixed the description of the postmortem_document_url parameter in the API docs
Fixed a bug that could cause Slack channel drop-downs to time out and display no results when searching
Fixed a bug where uninstalling a broken Sentry integration did not update the dashboard UI
Fixed a bug where incident channels that had been archived manually could not be interacted with via workflows after unarchiving them
Fixed a bug that prevented exported follow-ups from being unlinked when auto-export is enabled
Fixed a bug where archived phone numbers were showing as ready in the On-call readiness insights dashboard
Fixed a bug where some ClickUp and ServiceNow users were failing to sync in the catalog
Corrected date preview on date range picker when selecting preset date ranges
Fixed an issue where the escalation path UI was showing the wrong "Stop after" setting for a level, if you hadn't chosen any specific option
Fixed an issue where we incorrectly said or rather than and on the escalation timeline view on the dashboard, when referring to ways you'd be paged
We've fixed an issue where an alert source that was exported to Terraform may still include an attribute that you'd just deleted
We've fixed an issue where cover requests would default to requesting from deactivated users if they were still referenced on your schedule
We've fixed an issue where alert sources created in Terraform could return an unexpected diff after being applied, if you didn't specify an explicit else_branch
Fixed an issue linking alerts to CloudWatch if your alarm name included spaces in it