Slack

OAuthCommunication & SupportOrg connection

Org-level connection

Slack is connected once at the org level by an admin. The credential is shared across all groups that have been granted access — individual team members don't need to connect their own accounts.

How to connect

Click "Connect with OAuth" below to install the On Belay app to your Slack workspace. You'll be taken to Slack to approve the connection — no credentials to copy or paste.

Ready to connect?

Sign in to On Belay and open the Integrations page to add Slack.

Sign in →

Permissions (scopes)

These are the data scopes On Belay can be granted for Slack. Your org admin controls which scopes are enabled per group.

ScopeDescriptionAccess
channels:readList and read public channelsRead only
channels:historyRead public channel messagesRead only
groups:readList private channelsRead only
groups:historyRead private channel messagesRead only
im:readList direct messagesRead only
im:writeOpen direct message conversationsRead / Write
im:historyRead direct messagesRead only
mpim:readList group direct messagesRead only
mpim:historyRead group direct messagesRead only
chat:writePost messagesRead / Write
chat:write.publicPost to channels without joiningRead / Write
users:readView workspace membersRead only
users:read.emailView member email addressesRead only
files:readRead filesRead only
reactions:readRead emoji reactionsRead only
team:readRead workspace infoRead only

Troubleshooting

"redirect_uri_mismatch" error during OAuth
Your OAuth app's authorized redirect URIs don't include the On Belay callback URL. Add https://app.onbelay.ai/api/oauth-callback/slack to the allowed redirect URIs in your OAuth app settings.
"invalid_scope" error
The API or scope isn't enabled in your cloud project. For Google integrations, make sure the relevant API (e.g. Google Ads API, Search Console API) is enabled in Google Cloud Console for your project.
Connected but Claude can't access data
Check that your group has been granted access to this integration in On Belay → Groups → [your group] → Integrations. Also verify the specific scopes your group is permitted to use match what your query requires.

Still stuck? We're happy to help.

Contact support →