Note: Based on feedback, we're changing things up. We're making it simpler for developers to upgrade their apps, and creating a reliable app experience for customers. Read the Slack platform blog for more.
We're updating the way apps are built for Slack: we're laying the technical groundwork for better reliability and improved app management for workspace owners and admins. We have a few apps in our App Directory using this new framework, and additional apps will be added in the coming months.
Learn about the new app framework
This new framework is best described by the type of ‘tokens’ that apps are built with. A token allows an app to connect with your Slack workspace.
Currently, there are two types of tokens that developers can use for their Slack apps. The main difference between the two is how they connect to your workspace:
User tokens Most apps today are tied to individual members because they are built with user tokens. This means that apps mirror the access of the user who installs it, and are automatically added to every channel that the user is a part of. Most of the time this behind-the-scenes technical structure goes unnoticed, but if the member that installed the app leaves your workspace, the app that they installed will be disabled.
Workspace tokens With our new framework, instead of being tied to individuals, apps will connect to your workspace(s) via workspace tokens. The channels to which the app has access can be easily configured at a granular level. And since the apps are not tied to the installer, they’ll stay connected even if the original installer leaves your company and their Slack account is deactivated.