You must enable javascript in order to use the Slack API Documentation. You can do this in your browser settings.
Go to Slack

Developer preview: Workspace apps

Developer preview

Workspace apps are currently in developer preview. You are welcome to install as internal integrations or distribute to other workspaces, but we aren't yet accepting workspace app submissions for the Slack app directory.

This is a preview of the next generation of Slack apps. We want Slack apps to be ever easier to discover, trial, install, and upgrade and this new token type and permission model is the vehicle to that future.

Read our announcement to learn more about our motivation behind these changes and the benefits delivered to users and developers.

Try it now

Create a developer preview app

We aren't ready to accept workspace apps in the directory yet, but you're welcome to distribute them to other workspaces using Add to Slack and OAuth.

Looking for inspiration? The source code for the workspace token-based Slack app built by Github.

Read the documentation

Workspace tokens that power these new Slack apps work just like you're used to. Except they don't, so you'll want to catch up with this fresh documentation:

Look for these notices amidst content about different types of tokens for workspace-token specific information:

This treatment appears on OAuth scopes and Web API methods that support workspace tokens. Let it guide your way.

Developer preview

This feature is exclusive to our workspace apps developer preview.

What's new?

Workspace apps bring a number of refinements to the original model:

  • Workspace apps are installed on a workspace-level. Once installed on the workspace, the workspace owns the installation.
  • After installation, a workspace app can be added to public channels, private channels, direct messages, and other conversation types.
  • Your app is granted a single, potent access token per workspace that always reflects your app's current and full set of permissions and capabilities.
  • Upon installation, your app has the ability to open a direct message conversation with the installer of the app — an opportunity to let them know how your app works and offer a safe demo experience.
  • If the mood strikes you, your app may progressively ask for additional permissions as part of an interactive conversation experience, without requiring the heft of a full re-installation flow.
  • Scopes are granted workspace-wide but your app is limited only to the resources it's explicitly granted access to.
  • Link deeply into Slack and conversations with your app.
  • Sign in with Slack may now be used with workspace apps.
  • Workspace apps can perform operations on behalf of users.
  • Workspace apps can start conversations with users by requesting the conversations.app_home:create scope and then calling the fan-favorite chat.postMessage method.
  • Finally, the app is the bot and the bot is the app. Slack apps have a more user-like presence on Slack, like bot users of contemporary yore.

What's next

The launch of this developer preview is only the beginning.

Coming soon to a workspace token near you:

  • Permissions APIs improvements will expand permission upgrade requests to include asking for access to specific resources.
  • Automatic token rotation will add a new level of security of your app's access token.

You may distribute workspace apps and install them on any workspace, using OAuth. Slack does not yet accept apps in the developer preview into the app directory.

Longer term, we'll provide clarity around:

  • The migration plan. How will your existing apps migrate to workspace tokens? Good question.
  • More methods, more permissions, and more opportunities for user discovery.

Stay tuned

Keep track of where we're going:

Send us feedback! We love feedback! Email us at

Known issues

As with any nascent far-reaching platform feature, workspace tokens have a few bugs and unimplemented but planned features.

Feature Problem
OAuth Workspace tokens cannot yet call the legendary auth.test method.
OAuth Workspace apps' approved OAuth scopes are not listed in HTTP headers like X-OAuth-Scopes and X-Accepted-OAuth-Scopes and it's possible they never will be.
Documentation Some of the OAuth scopes listed as supporting workspace tokens do not actually support those tokens yet. Some methods claiming workspace token support don't support them yet. Personal experience will tell you for sure.

Find a new issue or have a question? Send us email to