πŸ” Granular Role-Based Access Control Settings for On-Call

Rootly adds a full set of On-Call permissions, so you can control access at a granular level and save permission sets as custom roles beyond Admin and User.

πŸ” Granular Role-Based Access Control Settings for On-Call
On this page

πŸ” Granular Role-Based Access Control Settings for On-Call

Our Roles and Permissions settings make it easy to manage user permissions at a granular level through a simple UI or via your SSO/SCIM provider. If you’ve wondered if we bring this same level of control to Rootly On-Call, the answer is yes!

We’ve created a full new set of permissions specifically for On-Call. In addition to the default roles of Admin and User, you can save any set of permissions as a New Role for consistency and ease. Not only can you control access to over 10 different pieces of On-Call functionality, you can specify between multiple access levels within each.

These settings are accessed in the same screen as your general Roles and Permissions (click your organization name/icon in the top left > Organization Settings > Roles and Permissions > On-Call). If you’d like to use SCIM to manage permissions via your SSO provider, visit our help docs for instructions to set that up.

What else shipped

πŸ†• Added rotation details to shift popover on the Edit Schedule screen. Now it’s easier for admins to see which rotation each calendar block originated from. πŸ’… Saving an on-call schedule during editing will no longer reset the calendar view back to today’s date. This will save users the need to cycle back to where they left off. πŸ’… Last used filters on Escalations Policies page will persist after user navigates away and return to page. πŸ’… Expanded confirmation modals to appear in configuration drawers (in addition to incident forms). Now all forms and drawers will warn users if they attempt to leave without saving their updated inputs. πŸ› Fixed issue with converted incident channels not being able to display in triage status. πŸ› Fixed intermittent issue with πŸ“Œ emoji command not adding the pinned message to the incident timeline. πŸ› Fixed incorrect navigation of follow-up action items links.

Your privacy choices

Rootly uses cookies from advertising partners to measure our ads and to show ads for Rootly on other sites. Some US state laws call that selling or sharing personal information. You can opt out of it for this browser here.

Analytics we use to improve this site stay on. Read Rootly's Privacy policy for more information.