Sandbox Environments

πŸ–οΈ Sandbox Environments

We are making testing your configurations, workflows, and integrations safer and easier with sandbox environments!

A standalone instance of Rootly connected to a separate non-production Slack environment.

An important consideration was ensuring you can seamlessly switch back and forth between production and sandbox environments that does not require logging in and out. You can do this with our organization switcher (top right drop down).

To get started, let your Partnerships Manager know and we'll provision one for you!


🌝 New & Improved

  • πŸ†• Action items are shown on Notion generated postmortems
  • πŸ†• Scheduled start and end times added to incident timeline page
  • πŸ†• Attribute for private incident visibility in Rootly API
  • πŸ’… Ability to click move to reorganize workflows instead of drag and drop
  • πŸ’… Action items are linked on postmortem tab for easier reference
  • πŸ› Fixed issue where workflow for Jira subtasks were not being triggered
  • πŸ› Fixed issue where disabling the automatic creation of incident channels was not respected
  • πŸ› Fixed issue where roles were not showing up for /incident test
  • πŸ› Fixed issue where some users were getting invalid triggers error on duplicate workflows


Rootly helps you respond to incidents faster as a team and learn to prevent them in the future.
wave