Developer sandboxes are Enterprise Grid environments that can be used to build against all of Slack's features both safely and securely, and without an additional cost. The ability to provision sandboxes is a benefit offered by the Slack Developer Program.
Ready to join? Follow the steps below!
Observe the welcome screen — you'll also receive a welcome email. Welcome to the Slack Developer Program! 🎉
Once your account is created and you're logged in, you'll be able to access your developer Dashboard. This dashboard features the latest development-related happenings at Slack, and is updated regularly.
To provision a sandbox, navigate to Sandboxes and click Provision Sandbox.
If you are not a member of a paid plan (the paid plan workspace must have been created at least 30 days ago), you'll be prompted to provide a payment method, but note that you will not be charged.
Enter the details for your sandbox and click Provision Sandbox again. Once created, your provisioned sandbox will appear below on the Sandboxes page.
To access your newly-provisioned sandbox, click its name and log in with your email address and the password you just created. Once you complete verification, your Sandboxes page will show a workspace with the same name as your sandbox.
Click Launch in Slack. Your workspace will show the following:
Your sandbox has been provisioned successfully. Happy building! 🏖️
A sandbox can have one of the following statuses:
Sandboxes have the following limits:
On the Sandboxes page, click the kebab menu to the right of that sandbox in the Active Sandboxes section and either:
On the Events page, you can view, filter, and search for upcoming events.
On the Settings page, you can:
Click Save profile to save your changes.
As part of the Slack Developer Program, you'll get access to an Enterprise Grid sandbox that allows you to explore all features, including automations. You'll also get early access to betas, and can develop and test apps and workflows in a dedicated, fully-featured development environment.
Developer sandboxes are intended to be used for development and application testing purposes.
Anyone can sign up for an account, and there are no costs associated with being a member of the Slack Developer Program. Sign up today!
Any developer enrolled in the Slack Developer Program can provision or delete a developer sandbox. However, in order to provision a sandbox, you must either be on a paid plan already, or you must provide a valid payment method for the account.
Yes. The payment method is used for identity verification purposes only; you will not be charged.
If you belong to an Enterprise organization and your Org Admin has enabled Allow developer sandboxes > Require approval for sandbox provisioning within your organization's settings, you'll need to make a request before you can provision a sandbox.
The steps for provisioning a sandbox will remain much the same, except that you can enter an optional reason for your request. After you click Request Access, your request will be submitted to your Org Admin.
Your Org Admin will review your request and, if approved, you'll receive a Slackbot notification that you can go ahead and provision your sandbox. If they deny your request or they have disabled sandbox provisioning for your organization, you'll see the relevant message displayed on both your Dashboard and Sandboxes pages.
Your Org Admin also has the ability to manage the sandbox you create—they can choose to archive it, extend its archive date, or delete it. You'll receive Slackbot notifications when any of these actions are taken.
If you are an Org Admin, once a developer within your organization submits a request to create a sandbox, you will receive a Slackbot notification to approve or deny the request. You may also configure default actions for incoming sandbox requests rather than having to review and manage requests one by one.
In addition, you can restrict who can join developer sandboxes with an allowlist of email domains (e.g., only users with a
Developer sandboxes are Enterprise Grid environments and offer the same features included with all Enterprise Grid plans, but with limitations imposed upon those features. Refer to sandbox limits for more details.
No. Each developer sandbox is distinct and has no connection to any other workspace that shares a common domain name.
You can provision up to 10 sandboxes over the course of 30 days, and you can have up to two active sandboxes at any given time. Sandboxes are active for six months by default. Refer to sandbox limits for more details. As long as you are still eligible to provision sandboxes, you can extend the lifespan of the active sandbox to another six months, every six months. Refer to sandbox statuses for more details.