Skip to content

fix(slack): correct the Slack auth provider scope list [TOO-2091] #1176

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
EricGustin merged 1 commit into from
Sep 3, 2026
Merged

fix(slack): correct the Slack auth provider scope list [TOO-2091] #1176

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion app/en/references/auth-providers/slack/page.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -48,10 +48,11 @@ The `conversations.history` and `conversations.replies` endpoints are now limite
- If you plan to use the [Arcade Slack MCP Server](/resources/integrations/social/slack), select the scopes below (include additional scopes for your application's authorization needs or custom tools, in any):
- `channels:history`
- `channels:read`
- `channels:write.invites`
- `chat:write`
- `groups:read`
- `groups:history`
- `groups:write`
- `groups:write.invites`
- `im:history`
- `im:read`
- `im:write`
Expand All @@ -60,6 +61,7 @@ The `conversations.history` and `conversations.replies` endpoints are now limite
- `mpim:write`
- `users:read`
- `users:read.email`
- Add all of the scopes above under **User Token Scopes**, not Bot Token Scopes. Arcade requests Slack credentials as user tokens, so scopes declared only for a bot token are never granted.
- Set the redirect URL to the redirect URL generated by Arcade (see below)
- Copy the client ID and client secret

Expand Down
Loading