Claude Tag’s September 24 personal-connector update changes where a team member can use their own access. It also makes a separate question more important: who can see the answer after private information contributes to a channel response? Anthropic’s announcement
Claude Tag, a beta product for Slack channels, previously used connectors attached by an administrator. Anthropic says a person can now ask Claude to use connectors linked to their own account, such as their calendar, drive or CRM access. The capability follows the requesting person’s access rather than requiring the whole channel to share every connected resource.
That does not make a channel response private. The source states that anything Claude posts is visible to everyone in the channel. Users can review each response before posting or choose auto mode, in which Claude requests review when it identifies sensitive content. Enterprise administrators will be able to require review for everyone, but that control is described as forthcoming.
The rollout is also staged. Personal connectors are arriving on Team plans, with Enterprise to follow. The announcement should not be read as completed availability across both plans on the publication date.
For unattended work, the old boundary remains. Personal connectors do not run scheduled routines or work Claude initiates on its own; those actions use the channel’s administrator-attached connectors. Activity through a personal connector appears in the source tool’s log under the user’s account, while shared-channel work remains under its service account.
My inference is that this creates two distinct governance decisions. One concerns the identity allowed to reach a resource. The other concerns the audience allowed to receive the resulting information. A team can use personal connectors for closely supervised requests while reserving shared connectors for work that must continue without a particular person present.
The announcement does not supply an independent assessment of sensitive-content screening. For a team, the useful takeaway is to make review expectations explicit before using personal access in shared conversations. The new capability reduces access friction, while channel visibility and unattended authorization remain separate limits.