Slack Enterprise Grid & Multi-Workspace Ready

🏭 Slack Enterprise Grid & Multi-Workspace Ready

We are excited to announce Rootly is the only incident management platform that is Slack Enterprise Grid ready.

Our support for Slack Enterprise Grid means organizations with multiple workspaces can unify how they manage incidents.

What does this mean for multi-workspace customers?

• Ability to create incidents from any workspace without needing to switch
• Users are seamlessly redirected to the incident channel after creating, no manual switching required
• Continue using /rootly commands from any workspace
• Get notified of incidents across all workspaces (through shared channels)
• All Workflows support multi-workspaces (e.g. page team in workspace A and B)
• Workaround locked down Slack permissions for creating new channels with incident specific workspaces

In Action

🌝 New & Improved

• 🆕 New Task in Workflows that allows you to invite Teams to incidents
• 🆕 Display who pinned events to the incident timeline
• 🆕 Added granular trigger events for Workflows beyond incident_updated, such as any variable like severity_updated, teams_updated, status_updated, and more
• 💅 UI improvements in Workflows that make adding Tasks more obvious
• 💅 UI improvements to status pages that ensure a status page has been selected first before publishing
• 💅 UI improvements to how Task names were labeled inside of Workflows to be even more clear
• 💅 Users that are logged into rootly.com they are automatically redirected to the Dashboard
• 🐛 Fixed issue where logging into PagerDuty via SSO put users in an endless loop
• 🐛 Fixed issue where Workflow runs where mislabeled as failed when it was actually canceled
• 🐛 Fixed issue where the incident variable {{ incident.title }} did not populate properly
• 🐛 Fixed issue with Email integration where sending an email did not always trigger an incident
• 🐛 Fixed issue with Pulses where we weren't properly ingesting team variables in some cases