Custom Role-Based Access Control (RBAC)

🔐 Custom Role-Based Access Control (RBAC)

Rootly is already the most secure and enterprise-ready incident management platform on the market by a margin.

Today, we are taking that further by introducing role-based access control (RBAC) to our customers.

Why? Not all incident data or access is as simple as having Admin and User.

For example, create a Security role only for your InfoSec team or an Observer role for read-only access to give customer support.

• Unlimited custom role creation with CRUD definitions
• Granular permissions (e.g. configurations, incident data, Workflows, integrations, etc.)
• Easily assign existing and new members new roles
• Limit access to both Slack app (e.g. /incident new) and Web UI
• Control who can access Private incidents (e.g. data breach)
• Out of the box popular roles pre-defined and ready to use

What else shipped

• 🆕 Ability to edit timestamps of events added to the incident timeline
• 🆕 Send Slack message Workflow task supports pinging individual users instead of just channels
• 🆕 We want to encourage users to keep opening incidents, now they can be marked as Canceled
• 🆕 Workflow condition status for Canceled incidents
• 💅 Made it easier to find the correct task type for Jira projects inside of Workflows
• 💅 More descriptive error messaging at sign up for incorrect user actions
• 💅 Infrastructure improvements on how we handle Slack commands internally, better reliability and performance
• 💅 Welcome message to greet you when you log into Rootly on Web
• 💅 Private incident alerts are always muted by default
• 🐛 Fixed issue where all Asana projects did not load for larger organizations
• 🐛 Fixed issue where invite to incident channel Workflow template had repeat and delay values set
• 🐛 Fixed issue where deleting incidents in Web did not immediately get reflected in the UI