Team Admin Permissions

In large organizations, teams work side-by-side to manage their incident response. Each team has its own responders, schedules, and escalation policies, and team administrators oversee their team’s responsibilities so they can respond effectively.

However without clear boundaries and ownership between teams, it’s easy to accidentally change another team’s configuration—like a crowded kitchen where the pastry chef accidentally adds sugar to the saucier’s dish. These mix-ups slow down response times and lead to costly organization-wide impacts.

What's new?

Introducing Team Admin Permissions. System admins can now grant admin permissions to team members: team admins are able to create and make changes to their team's schedules and escalation policies.

Teams now have a clear separation of ownership, reducing the risk across your entire organization.

Get started with Team Admin Permissions

To get started with configuring your team admins, login to Rootly:

1. Navigate to Configuration > Teams and create your Teams.
2. Add your team members, then select your Team Admin.

What else shipped

New

• Alerts can now be retriggered in the mobile app, waking responders back up when they’ve fallen asleep.
• Added the ability to surface a Rootly Metrics Dashboard in Datadog.
• Added the ability to quickly replace a deprovisioned user while editing on-call schedule.
  

Improvements

• Liquid reference to impacted functionalities (i.e.{{ incident.raw_functionalities }}) now return the owning team(s) of that functionality. This can be used to dynamically set the owning team(s) for an incident whenever the impacted functionalities are known.

Fixes

• Fixed issue with manually lining ServiceNow incident to Rootly incident.
• Fixed intermittent issue with NewRelic alerts not auto-resolving.
• Fixed incorrect ordering of escalations_levels returned from the listEscalationPolicies API.