Claude Tag adds personal connector support in Slack channels

Claude Tag (beta) now allows users to leverage their own personal connectors when interacting with Claude inside a Slack channel. Previously, Claude could only access connectors that an admin had explicitly attached to the channel, a restriction designed to keep access tied to the channel rather than the individual.

How it works

When a user asks Claude to access data behind their own login—such as a private Google Drive document, calendar, or CRM account—Claude uses that user's personal connector. This happens separately from the channel's shared work. The user retains control over how the output is presented:

• Review Mode: The user reviews each response before it is posted to the channel.
• Auto Mode: Claude posts automatically unless it detects sensitive content requiring review.
• Admin Controls: On Enterprise plans, admins can enforce review mode for all users.

Governance and logging

Personal connectors offer admins flexible governance options. They can choose to rely on shared agent identities, restrict access to personal connectors to leverage existing role-based permissions, or configure tools individually. All actions taken via a personal connector are logged under the user's account, similar to direct-message interactions, while the channel's own automated tasks remain under the channel's service account.

Limitations and use

Personal connectors do not support unattended actions. Tasks that require automation or are relied upon by the entire channel must use shared connectors attached by admins. Personal connectors are best suited for collaborative work where individual access to private data is needed, such as drafting documents or checking personal calendars, while shared connectors handle operational tasks like on-call support or CI/CD monitoring.