
Claude Tag now uses your personal connectors in shared Slack channels
Anthropic has updated Claude Tag (beta) so Claude in a shared Slack channel can use the personal connectors a user linked to their own account, not just the tools an admin attached to the channel. Nobody else can use them.
Anthropic announced on September 24 that Claude Tag, the beta integration that puts Claude in Slack channels, can now use the connectors a user linked to their own account, not only those an administrator attached to the channel.
Access follows the person, not the channel
Until now, Claude in a channel could reach only the tools an admin had wired up, and most organizations kept that list short on purpose. With the update, a user can ask Claude in a shared channel to check their own calendar, Google Drive files, the CRM accounts assigned to them, or changes deployed to staging. Only the owner of a connector can trigger it, so teammates in the same channel cannot borrow someone else's connections.
In Anthropic's example, a user named Priya works in a channel connected to GitHub and asks Claude to compare her Google Drive planning document with the work already shipped. Claude reads the merged pull requests through the channel's connector and the private document through her own connector, then posts what is done and what is still open.
Review before posting
Users choose how answers surface: they can review every reply before it is posted, or use auto mode, in which Claude posts automatically unless it flags sensitive content and holds it for review. On Enterprise plans, admins will be able to require review for everyone in a channel. Anthropic also lists governance options for admins: a shared set of tools under an agent identity, personal connectors only so access follows role-based permissions, or a tool-by-tool decision.
Limits and rules
Personal connectors do not run unattended: scheduled routines and anything Claude starts on its own still use the connectors an admin attached to the channel, so overnight monitoring and on-call incident response keep depending on shared tools. Anything Claude posts is visible to everyone in the channel. Activity through a personal connector appears in that tool's own log under the user's account, while the channel's work stays under its service account. A connector can be disconnected at any time.
Availability
The feature is rolling out now on Team plans, with Enterprise to follow. There is no separate installation step: the first time a request needs one of your connectors, Claude asks for permission and reuses it in that thread.
SiTech — AI-powered web development
We build fast, modern websites and bring AI into real business workflows. Have a project or a question? We'd love to help.