Required scopes on installation
All of the following scopes are requested on first installation of our Slack bot, and are required for our app to run.app_mentions:read
Respond to direct mentions to our bot from Slack users.
bookmarks:read
See the bookmarks we set within incident channels.
bookmarks:write
Set bookmarks in incident channels (such as the alert that triggered the incident).
canvases:write
Create canvases in incident channels.
channels:history
Read content in Slack channels we’re added to, including messages users pin in their incident channel.
channels:manage
Create incident channels.
channels:read
Read incident channel names.
chat:write
Write messages and updates in channels we have access to.
chat:write.public
Send announcements to public channels we haven’t been added to (such as the incident announcement channel).
commands
Add slash commands, such as
/inc so you can interact with our bot.files:read
Read files shared in channels we have access to (such as images in incident channels).
files:write
Upload files to channels we have access to so we can share insights reports and other materials.
groups:read
See private incident channels we are part of.
groups:write
Post to private incident channels we are part of.
groups:history
Read messages in private incident channels we’re added to.
im:history
Read DMs that are sent to the incident bot.
links:read
View URLs in messages.
links:write
Show previews of URLs in messages from our bot.
pins:read
Read pinned messages so we can save them to the incident timeline.
pins:write
Write new pins to a Slack channel, such as the incident welcome message.
reactions:read
See when users have reacted to messages to trigger an action such as creating follow-ups.
reactions:write
Add reactions to messages, such as marking GitHub pull requests as reviewed.
teams:read
Read your organization’s name and icon.
users:read
Read your organization’s users.
users:read.email
Match user accounts with other services, such as GitHub.
users.profile:read
Read user avatars so they can be displayed in our UI.
usergroups:read
List all user groups for syncing schedules.
usergroups:write
Sync on-call schedules into your Slack user groups.
Optional additional scopes
We don’t request any of these on installation, but you can choose to provide them later.channels:join
Rejoin incident or announcement channels if we lose access. If this isn’t granted, users will have to manually add our bot to any channel they want to interact with us in. If you’d like to configure this, contact us at help@incident.io.
Privileged access scopes
Depending on your Slack workspace settings, bots and regular users may be restricted from taking certain actions. If your organization’s Slack configuration requires admin access for certain operations, you can choose to additionally provide these scopes, otherwise some incident.io features may be degraded. You can find out more details about each of those scopes here These scopes are User Scopes, which means you’re granting us permission to use them on behalf of a specific user, rather than as our bot. To use any of these, you need to configure a Slack admin for our bot These include:channels:write
Create and archive public incident channels, if this requires admin access in your Slack workspace.
groups:write
Create and archive private incident channels, and remove member’s access to them if it’s revoked within incident.io.
usergroups:write
Sync on-call schedules into your Slack user groups, if this requires admin access in your Slack workspace.
admin.conversations:write
Convert channels between public and private, to match the visibility of an incident.