Claude Tag now supports personal connectors in channels
- ID
- 28291
- Status
- summarized
- Published
- 24 Sep 2026, 8:00 AM
- Fetched
- 25 Sep 2026, 6:53 AM
- Provider
- Claude
- Category
- ai-labs
- Original URL
- https://claude.com/blog/claude-tag-now-supports-personal-connectors-in-channels
- Source URL
- https://raw.githubusercontent.com/leontloveless/ai-rss-feeds/main/feeds/claude.xml
Summary
- Score
- 4.5
- Created
- 25 Sep 2026, 6:53 AM
- Tags
- Audience
- developersvibe_codersai_agent_userssaas_founders
What happened
Anthropic announced that Claude Tag (its beta Slack integration) can now use a user's own personal connectors for requests made in a channel, not just the connectors an admin attached to the channel. The stated example: someone asks Claude to check their private Google Drive plan against merged pull requests from the channel's GitHub connector, and Claude reads the Drive doc under that person's own access. Personal connectors are rolling out now on Team plans, with Enterprise to follow; admins get options including requiring review for everyone, or routing shared tools under an agent identity.
Why it matters
If your team already runs Claude Tag in Slack, the access model just changed from 'what the channel can see' to 'what each asker can see' — which means you should decide now whether to keep granting a broad shared tool set or rely on existing per-user role-based access, since admins on Enterprise can force review-before-post while Team plans get auto mode that posts unless Claude flags sensitive content. This also removes the common blocker where a private doc, calendar, or CRM record couldn't be pulled into a channel answer without an admin widening channel-level permissions.
Discussion angle
Personal connectors mean an agent's effective permissions now depend on who is asking rather than where it is running — worth discussing how that changes audit trails, and whether auto-post mode is acceptable when the output may quote data only one person could open.