Back to Changelog
Back to Changelog

January 12, 2023


Multi-Organization and Workspace Support

Multi-Organization and Workspace Support

🏘 Multi-Organization and Workspace Support

We are excited to launch the ability to have multiple organizations and workspaces of Rootly under the same roof and license.

Why? Companies and enterprises are not one dimensional in their needs. They are comprised of multiple departments, sibling organizations, acquisitions, and all of whom might have wide ranging requirements when it comes to how incidents are managed.

By having separate workspaces, organizations, and instances of Rootly, this unlocks the ability to not step on each others toes. For example, the NOC department will likely handle incidents differently from the rest of the company. The sister company that was acquired that will remain separate from the parent org has different tools they'd like to use. The SRE team that has a sandbox environment to experiment with new processes before rolling to production.

Use the same Slack workspace across all of your Rootly organizations! Upon incident creation, users will be asked to select which organization they would like to create their incident in (see header image).

Regardless of your organizational complexity, the UX for responders is simple and intuitive.

  • Be part of and switch between multiple organizations within the Web Platform without needing to logout
  • Support for multiple domains
  • Plug in the same or different integrations as needed (e.g. company uses the same Jira but different PagerDuty accounts)
  • User and usage is counted towards a single license

Existing users - to setup a new organization, contact your account team via Slack or Once enabled, on the Web Platform > Profile > Switch Organization. The ability to switch organizations on Slack will appear after you've integrated the same Slack workspace across multiple Rootly organizations automatically.

🌝 New & Improved

🆕 API endpoints to mark the incident as started, mitigated, resolved, and canceled
🆕 Default postmortem timeline is in chronological order and incident timeline is in reverse chronological order (most recent first)
💅 Infrastructure improvements to how we handle webhooks
💅 Significant infrastructure improvements around increasing test coverage
💅 Incidents deleted by accident can be recovered by requesting to or in your teams shared Slack channel with Rootly
🐛 Fixed issue where form fields where not being respected on the Web Platform when disabled
🐛 Fixed issue where some Slack redirect links were incorrect

Previous post
Previous post
You are viewing the latest post

👯‍♀️ On-Call Shadowing

🔌 Generic Webhook Alert Source

🔒 Lock Individual Workflows

🐦‍⬛ Round Robin Escalation Policies

🚨 Alert Sources

🔔 Configurable On-Call Shift Reminders

🪄 Dynamic Forms

🔐 Granular Role-Based Access Control Settings for On-Call

✉️ Emails as an On-Call Alert Source

🗓️ View Multiple On-Call Schedules Together

🤝 Partial Shift Overrides in Rootly On-Call

🏗️ Terraform + API Support for Rootly On-Call

🦉 Rootly x Thena Integration

🎬 New Full Platform Tour on

🔦 Drop-down Search in Escalation Policy Builder

🦊 GitLab Integration

Update Custom Incident Fields Using Workflows

🤖 Ask Rootly AI (+ More New AI Features!)

Rootly AI Editor: Fix Typos, Grammatical Errors, and Wordy Text Instantly

📊 Dashboard Sharing Permissions

✍️ Customize Your Wordbank for Automatic Incident Title Generation

🧠 Smart Defaults for Jira

🔌 The Rootly Plugin for Zendesk

🪄 Rootly Retrospectives

⚡ Command Palette: Lightning Fast Navigation with a Single Keyboard Command