Slack
Which Slack permissions Attributed requests and why
A breakdown of the OAuth scopes Attributed asks for and what each one does.
Which Slack permissions Attributed requests and why
When you click Add to Slack, Slack shows a permission screen. Here's what each scope is for.
| Scope | What it lets us do | Why we need it |
|---|---|---|
chat:write | Post messages as the Attributed bot | To deliver findings and Implementation Packs |
chat:write.public | Post in public channels the bot hasn't been added to | So you don't have to manually invite the bot to public channels |
channels:read | List public channels | Powers the channel picker during install |
groups:read | List private channels you're a member of | Powers the channel picker for private channels |
team:read | Read workspace name and icon | Shown in Integrations so you can tell workspaces apart |
incoming-webhook | Post to a specific channel via webhook | The destination channel you select during install |
What we do not request
- We do not request
channels:historyorgroups:history— we never read messages from your channels. - We do not request
users:read.emailor any user data scopes beyond what's needed to identify the installer. - We do not request
files:write— we don't upload files to Slack.
See our privacy policy for how the data we do store is handled.
Still need help?
Email support and we'll get back within one business day.