More flexible Slack Enterprise Grid setups

We’ve made it easier than ever to use incident.io with Slack Enterprise Grid. Now, you can enjoy more complex and flexible relationships between your workspaces and organizations.

If you're already using Slack Enterprise Grid, you know that you can manage multiple Slack workspaces within a single incident.io organization. This is especially handy for large companies that have picked up a few extra Slack workspaces along the way.

In addition to this, we've now added the ability to host multiple incident.io organizations within a single Slack Enterprise Grid. This is perfect if you're on our Enterprise plan because you can easily juggle a production and a sandbox environment from different workspaces on the same Slack Enterprise Grid. It's a great way to safely test and train while keeping your main incident management running smoothly.

Whether you're bringing together new teams or keeping different departments organized, our platform now makes it a breeze to set up and manage everything under one roof. If you want to dive deeper into what our Enterprise offering can do for you, check out our website.

🚀 What else we’ve shipped

🆕 GitLab and GitHub incident ticket titles can now use multiple variables, e.g. both the incident reference and name

🐛 Status page subscription emails no longer get sent after a page is archived

🐛 Catalog attributes now can't be deleted when referenced by incident types

🐛 The "close" button on catalog entries now takes you to the right URL

🐛 Improved error messages if you use the manual escalation form to escalate to no one

💅 Fixed an issue where applied filters were overflowing incorrectly