Team-scoped API keys

We now allow you to create API keys that are restricted to managing resources (schedules, escalation paths, alert sources, alert routes) owned by a specific team.

This is useful when a team might want an API key to manage their on-call schedules via Terraform, without accidentally modifying a different team’s schedules. They can now create a key with account-level read access, but team-scoped write access to schedules.

API keys can have either global permissions, team-scoped permissions, or a combination of the two. Users can create keys with the permissions that they, themselves have.

We also gave the API keys settings page a bit of a glow-up while we were here!

Editing API keys

Previously, if you wanted to make changes to an API key (rename, add a new scope, remove a scope) you’d have to delete and create a new one, which was less than ideal. Now, if you have the allowed permissions, you can edit them!

AI suggestions in Microsoft Teams

Customers who use Microsoft Teams now benefit from proactively generated AI suggestions. This includes suggested updates, summaries and follow-ups within the incident channel.

See our help docs to learn how to enable these for your account.

Choose whether On-call notifications bypass DND

Until now, we've assumed if you had an "app" notification in the "High urgency" section, we'd page you loudly and bypass do-not-disturb, and then a low-priority page would just quietly notify you.

Now, you can customize the notification in each section - allowing you to set up such where you get paged via a quiet notification and only page loudly after a minute.

Filter the homepage by your teams

We've replaced the "All", "Participating" and "Mine" toggles with a new dropdown that also contains the option to filter the option to your teams. Like before, this remembers your selection, so if you refresh the homepage it'll keep you on the option you'd chosen previously.

What else we've shipped