OAuth scopes allow you to specify exactly what access your app needs to perform its functions. In the previous example, we requested the bot scope, which gives our bots access to all the actions a bot user can perform. For example, the channels:history scope gives us access to the channel's chat history and users:read allows us to access the full list of users in the team. There is a long list of scopes available (which you can review at https://api.slack.com/docs/oauth-scopes), but we will focus on the three most likely to be used scopes in our apps:
bot: This provides a bot token, allowing us to connect to the team as a bot userincoming-webhook: This provides an incoming webhook tokencommands: This provides a Slack token, which we can use to ensure that the incoming slash command requests are valid
Note
Scopes of the bot variety automatically include a subset of other scopes needed for the bot to perform. For more information, visit https://api.slack.com/bot-users#bot-methods.
Multiple...