Anthropic lets Claude use personal tools in Slack channels
Anthropic began rolling out personal connectors for Claude Tag in Slack channels on 24 September, letting a person ask Claude to combine their own calendar, drive, CRM or deployment access with tools attached to a shared channel. Previously, the beta channel assistant could use only connectors an administrator attached to that channel. The feature is rolling out on Team plans, with Enterprise support to follow. It addresses a concrete problem in collaborative AI: much of the information needed to answer a team question belongs to one member and should not become a standing permission for everyone in the channel. Claude can now use that person's access for their request while keeping the channel's shared tools under their separate service identity.
Anthropic illustrated the workflow with a team member comparing a private Google Drive project plan against merged pull requests visible through the channel's GitHub connector. Claude can read the plan using the requester's personal connection, read repository work through the channel connection and prepare a response about what shipped. The requester can review the answer before it posts, or select an automatic mode in which Claude posts unless it detects sensitive content needing review. Anthropic says Enterprise administrators will be able to require review for everyone. This distinction matters because obtaining an answer and publishing the source material to colleagues are different permissions. The user controls the handoff into the shared conversation.
The company's design keeps tool logs under the identity that performed the work. Actions through a personal connector appear in that user's connected service account, while channel-level work remains under the service account administrators already monitor. Anthropic says ‘nobody else can use’ another member's personal connections. It also gives administrators a choice among a shared agent identity, members' role-based access or a mixture by tool. Those are operational controls, not a claim that Claude can freely disclose everything it sees: the usefulness of the feature depends on allowing enough cross-source context to answer a question while controlling what may be posted back to a group.
The product update comes as AI assistants are competing to join work where discussions already happen. Slack channels provide a natural place for a request about deadlines, sales accounts or code changes, but data access is fragmented among people and systems. A channel-only connector set may have been too restrictive for many useful questions, while giving the bot broad shared permissions would weaken the organization's existing access rules. Personal connectors offer a middle path tied to the requesting employee. The rollout could make Claude Tag more useful without requiring a company to replicate every private permission in a channel configuration. It also adds a review step that could slow routine replies if applied universally.
Anthropic's broader plugin and marketplace announcements in the same week aim to make tools easier to discover and publish. Personal connectors in Tag give those connections another distribution surface: a tool already linked to an individual's Claude account becomes usable in a shared Slack conversation for that individual's request. The company has not published a usage count or revenue effect for this feature. Its significance lies in the permission architecture for a common enterprise workflow, where a team's shared task depends on data that only one person may see. If the design works reliably, it could increase the value of existing connections and reduce the need for teams to copy sensitive material into a prompt manually.
Analysis
The feature turns a limitation of channel bots into a potential advantage: Claude can answer a richer team question while respecting the individual's existing access rights. That can raise engagement with Anthropic's paid Team and later Enterprise plans and increase the return on its connector ecosystem without securing a new data agreement for each channel. The economic risk is approval friction: mandatory review protects against disclosure but may reduce the speed that makes a channel assistant attractive. Keeping personal and service-account activity separate in logs is valuable for enterprise audit, especially when Claude moves from reading information to taking actions. Anthropic's differentiation will depend on reliably preserving that identity boundary during real mixed-source tasks.