Anthropic has updated Claude Tag, its beta feature for adding Claude to Slack channels, so that Claude can now use the personal connectors an individual user has linked to their own Claude account, not just the connectors an admin attached to the channel.
Before this change, Claude in a channel could only reach tools an admin had explicitly wired up, which meant organizations kept channel-level connector lists short and access followed the channel rather than the person. Now a user can ask Claude, in a shared channel, to check their own calendar, drive files, assigned CRM accounts, or staging deploys, and only they can trigger access to their own connectors — teammates in the same channel cannot use someone else's connections.
Users control how responses surface: they can review each answer before it posts, or use auto mode, where Claude posts automatically unless it flags the content as sensitive and holds it for review. On Enterprise plans, admins will be able to mandate review for everyone in a channel.
Anthropic's example: a user named Priya, in a channel connected to GitHub, asks Claude to check her personal Google Drive planning doc against merged pull requests. Claude reads the shipped work through the channel's shared GitHub connector, then separately reads Priya's private doc through her personal Google Drive connector, and posts a comparison — something the integration couldn't do before this update, since the doc was only accessible to Priya.
Activity through personal connectors is logged under the user's own account in that tool's log, the same way direct-message activity with Claude is recorded, while the channel's own connector work stays under its existing service account. Users can disconnect a personal connector at any time.
Personal connectors do not run unattended: scheduled routines or anything Claude initiates on its own still rely on connectors an admin attached to the channel, so use cases like on-call triage or overnight monitoring continue to depend on shared, admin-provisioned connectors rather than personal ones.
The feature is rolling out now on Team plans, with Enterprise availability to follow. There is no separate installation step; Claude asks for permission the first time a request needs a personal connector, then uses it going forward in that thread.