Skip to main content
A sandbox environment is a separate, fully-featured incident.io organization designed for safely testing configuration before rolling it out in production.

​
How it works

The sandbox is a completely independent incident.io organization from your production instance, connected to a completely different Slack workspace or Microsoft Teams tenant for testing purposes. Because it’s a separate organization, configuration cannot be directly promoted from sandbox to production. Teams typically experiment in the sandbox, then recreate what works in production. You can use Terraform to manage configuration as code across both environments and automate this.

​
How to request a sandbox environment

Sandbox environments are available to customers on the Enterprise plan. To set one up:
  1. Have a test Slack or Teams workspace — set up a new Slack workspace (a free workspace is fine) or designate a separate Microsoft Teams tenant for testing.
  2. Install incident.io — install the incident.io app in the new workspace via incident.io/trial.
  3. Let us know — share the workspace name or URL with your Customer Success Manager, or contact support, and we’ll mark the account as a sandbox.
If you use SAML SSO, avoid enabling it on your sandbox environment. SAML will automatically redirect users to your production instance based on their email domain. See SAML SSO for more details.
If you just need to test your configuration or run a practice incident without setting up a full sandbox, use test incidents instead.