| The rundown | |||
|---|---|---|---|
| Read this if: | You're working with Enterprise Grid or multiple workspaces. | ||
| Read first: | Apps for enterprises | ||
Sometimes, in a life of green lawns, you need a place to try your hand at building the sand sculptures you've always dreamed of. Enter the sandbox, a safe space for you to build and learn before you start spending all your time at the beach to build ever greater structures.
For apps, the sandbox is a space that gives you a sense of Slack's Enterprise Grid without fear of making a mess in live workspaces. An Enterprise Grid sandbox allows you to test the functionality of shared channels and multiple Slack workspaces on Enterprise Grid.
If you've made it here, you've likely already learned a thing or two about Enterprise Grid and are curious to know more. To get started, request a sandbox using this signup form.
Once you have your sandbox, you can use these guidelines to get it configured and working.
Your Enterprise Grid sandbox comes with some limitations. As you get started testing, there are a few things you need to know.
After you submit the sandbox request form, you will be provisioned two – yes, two – separate Enterprise Grid sandboxes. Each sandbox will be provisioned in a separate email to your Enterprise Organization's primary owner, as specified on the signup form.
If you have questions as you start to use your sandbox, please let us know at feedback@slack.com, and the Developer Support team will get back to you as quickly as possible.
The developer instance of Enterprise Grid is a development sandbox with limitations around data retention and user account creation. These limitations exist because the sandbox isn’t intended for normal use, it is for testing purposes only. Slack will retain messages and files shared in the sandbox for only three days after they’re created.
