Here's what we learned from you: to provide the best developer experience, we must make it simpler to create Slack apps. The extended developer preview is now closed.
We know that some beloved features entered into the world via workspace tokens, including umbrella
conversations:* scopes and token rotation. Fear not: over the next few months, we'll make sure that these features land gracefully in the world of classic Slack apps.
Read our announcement to learn more about our motivation behind these changes.
Workspace apps may no longer be created. Slack will not accept new workspace apps into the app directory going forward, but you're welcome to distribute them to other workspaces using Add to Slack and OAuth.
These documents explain how workspace apps departed from traditional Slack apps:
These notices marked content about different types of tokens for workspace-token specific information:
This treatment appeared on OAuth scopes and Web API methods that support workspace tokens.
Workspace apps departed in a number of ways from the original model of Slack apps:
conversations.app_home:createscope and then calling the fan-favorite
The developer preview for workspace apps has ended. Keep track of where we're going with the future of the Slack platform:
/feedin your favorite Slack channel.
Send us feedback! We love feedback! Email us at firstname.lastname@example.org.
As with any far-reaching platform feature, workspace tokens have a few bugs and unimplemented features.
|OAuth||Workspace tokens cannot yet call the legendary
|OAuth||Workspace apps' approved OAuth scopes are not listed in HTTP headers like
|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 email@example.com.