Need a safe place to play before you make changes to your Enterprise Grid instance? Enter the sandbox, a safe development space for you to build and learn in.
A sandbox allows you to test and develop your app against a Slack Enterprise Grid instance, complete with multiple workspaces, without fear of making a mess in production.
To get started, request a sandbox based on one of the criteria listed below:
If you're a developer looking to internally test Slack for your production instance, use this sign up form.
If you're a Slack/Salesforce consulting partner, use this sign up form.
After you submit the sandbox request form, you will be provisioned two separate Enterprise Grid sandboxes. You'll receive a separate email for each, sent 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 firstname.lastname@example.org, and the Slack Support team will get back to you as quickly as possible.
Once you have received your sandbox, you can use these instructions to get it configured and ready to use.
After the Primary Org Owner creates their account, they should create at least one workspace.
Grid requires all users to use SSO, which means admins must set up an IdP. If you already have an IdP, you are welcome to use that one on your sandbox.
If you don't have access to an IdP, we offer a Slack app, Simple IdP, that mocks an IdP to enable easy creation and management of user accounts. If you opt to use Simple IdP, all user accounts for your Grid sandbox must be created with the test IdP, and it will not be possible to create and use accounts outside of the test IdP app. Instructions for managing accounts may be found below.
Go to https://slack-test-idp-for-sandboxes.herokuapp.com and install the app. Make sure you install the app on the org, and not a workspace!
There are some pre-configured settings from Simple IdP you need to copy into your sandbox's SSO configurations.
You can add as many auto-generated users as you like through Simple IdP. For the most part, these auto-generated users are good for testing your app. However, if you need more than one real person signed into your org at a time, you’ll need to take a few extra steps because of how the Simple IdP works.
Each person that you want to be able to sign into the sandbox will first need to sign in as the primary owner, authenticate the Simple IdP app, sign out, and then sign in as themselves.
First, go to "Create a custom user" and provision an account for them in the Simple IdP. They will now show in the “Organization Members” list at http://[org-domain].enterprise.slack.com/manage/people
Add that user to a workspace and have them follow these steps:
After that, they'll remain logged in.
If you have questions as you start to use your sandbox, please let us know at email@example.com, and the Slack Support team will get back to you as quickly as we can.
As a test instance, your Enterprise Grid sandbox comes with some limitations.
For those building third party apps on Slack, 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.
Slack/Salesforce consulting partners will not have data retention restrictions but will have user account creation limitations. The sandbox isn’t intended for normal use and should only be used for testing purposes.