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.Set the status, title and suggested prompts in assistant threads, so you can chat with incident.io from Slack’s
assistant sidebar.
Read content in Slack channels we’re added to, including messages users pin in their incident channel.
Send announcements to public channels we haven’t been added to (such as the incident announcement channel).
Post messages with a custom username and avatar, so features like Scribe and Investigations can appear with their own
bot identities.
Read your workspace’s custom emojis, so you can use them in messages we send, templated text, and custom reactions.
Optional additional scopes
We don’t request any of these on installation, but you can choose to provide them later.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:Create and archive private incident channels, and remove member’s access to them if it’s revoked within incident.io.
Sync on-call schedules into your Slack user groups, if this requires admin access in your Slack workspace.