Where Claude reads and posts
Claude reads and posts only in channels it has been added to, and in direct messages. Any workspace member who opens a direct message with Claude receives its welcome message, whether or not they’ve linked a Claude account. Installing the app does not add it to any channel. A member can add Claude to a channel in one of two ways:- Invite it with
/invite @Claudein the channel - Select Add to channel on a channel Claude suggests in a direct message. Claude’s welcome message, the introduction it posts when a member first opens a direct message with it, suggests public channels this way.
channels:join scope. Slack’s audit log records the join as the Claude app, with no inviter shown; neither the member’s selection nor the matched pattern is visible in Slack’s log. If you see a join in the audit log that no one can explain, a member selected one of these buttons or an auto-join pattern matched. Outside those two paths, Claude does not join channels on its own.
Reading a channel’s full history requires being added there. Workspace search can surface public-channel content, the same as any app with the search scope.
Slack Connect channels (shared with another company) are always excluded, regardless of configuration.
Requested scopes
The app requests bot scopes for reading and posting in channels it’s a member of, reactions, files, canvases, user lookup, and public-channel search. Slack’s install consent screen shows the full current list; treat that as the canonical reference, since the set can change between releases. Two scopes a Slack admin commonly asks about:channels:joinlets Claude add itself to a public channel when a member selects one of its suggested-channel buttons, or when the channel’s name matches an auto-join channel pattern an admin set. It cannot join private channels this way.users:read.emaillets Claude read a member’s profile email. Claude uses it for checks such as the email domain when a member connects their Claude account. It does not connect accounts; a member still runs the Connect step in Slack.
What installing does not grant
Credentials for GitHub, Google Drive, a data warehouse, or anything else are provisioned separately by a Claude organization Owner and live on Anthropic’s side rather than in Slack. It responds when @-mentioned, and may respond to other messages it judges warrant a reply.After you install
Post@Claude connect in any channel with no other text, or send connect on its own in a direct message with Claude, and give the code it returns to whoever asked you to install. That code is what pairs your workspace to their Claude organization; it expires after 15 minutes.
Pick a channel that belongs to just your workspace. Claude can decline to reply in guest and shared channels.
Related resources
- Security and data handling: where credentials are stored and what leaves your workspace
- Pair your Slack workspace: what the Claude Owner does with the code you send