Slack Permissions Scopes for the Round Robin Bot

You can learn about the different Slack permission scopes requested by our app, Round Robin, and what functionality they enable.

To use Round Robin in Slack, a Workspace Admin needs to install the app. When installed, the app will request access to different permission scopes that enable different functionality. By default, Round Robin asks for the minimum scopes needed for all product functionality.

Round Robin uses the latest version of the Slack API with Granular Bot Permissions.

app_mentions:read

The app:mentions.read scope is requested as a bot token. This scope lets Round Robin know when the bot is mentioned in a channel it's in and responds with the appropriate message.

channels:read and channels:manage

The channels:read and channels:write are requested as a bot token. The channels:read scope is needed to let the bot see the channels list in the rotation management window and to get basic info about public channels in a workspace. We also use the scope to verify the kind of channel the bot is interacting with to execute the proper communication towards the users. The channels:manage scope is needed to let the bot set the topic of a public channel with the informations related to the rotation.

chat:write and chat:write.public

The chat:write, and the chat:write.public scopes are requested as a bot token. The bot token allows Round Robin to post messages about rotations in channels the bot was invited to and to other public channels it is not a member of.

commands

The commands scope is requested as a bot token. This scope enables using the /rr slash command plus the Slack Action.

groups:read and groups:write

The groups:read and the groups:write scope are requested as a bot token. The groups:read scope is needed to let the bot see the private channels it is member of in the rotation management window. We also use the scope to verify the kind of channel the bot is interacting with to execute the proper communication towards the users. The groups:write scope is needed to let the bot set the topic of a private channel is member of with the informations related to the rotation.

team:read

The team:read scope is requested as a bot token. This scope let the bot read the team info and listen to team event, for example to change the team name in the web app if the team name changes.

usergroup:read and usergroup:write

The usergroup:read and usergroup:write scopes are requested as bot token. The usergroup:read scope is needed to let the bot or the user list the current user groups to enable the assignment to a rotation. In contrast, the usergroup:write scope is used to edit user groups' names and compositions to manage the on-duty group feature.

users:read and user:read.email

The users:read and user:read.email scopes are requested as bot tokens. The users:read scope is needed to let the bot list the workspace users during rotation creation and editing. The user:read.email is needed to allow the bot to get the user's email and store it for connectivity with external services, such as Pagerduty. No communication happens outside Slack. This feature is still under development.

team:read

The team:read scope is requested as a bot token. This scope lets the bot read the team info and listen to team-related events, for example, to change the team name in the web app if the team name changes.