Anthropic says a person who invokes Claude Tag in a Slack channel can now use their own connected tools without giving the whole channel access to those tools. The answer may still be posted to everyone in the channel, and unattended tasks still need shared connectors.
RELATED BUYER PROFILEReview Claude plan boundaries and test-pending buyer evidencePricing · access · strengths · limitations →RELATED DECISION GUIDESet connector permissions and response-approval boundariesWorkflow · evidence · risk · governance →CONTINUE THE DECISIONRequest signed-in access, data and audit evidenceEvidence · workflow · next action →CONTINUE THE DECISIONPilot one reviewed, read-only channel requestEvidence · workflow · next action →CONTINUE THE DECISIONMeasure seats, connector licences and review timeEvidence · workflow · next action →CONTINUE THE DECISIONSee the separate small-business workflow launchEvidence · workflow · next action →What you need to know
- Anthropic announced the connector change on 24 September 2026; it is rolling out on Team, with Enterprise to follow
- Only the requesting person can use their personal connectors, but any posted answer is visible to channel members
- Scheduled or self-started work cannot use personal connectors; those routines need admin-attached shared connectors
Short answer: access is personal, output is shared
On 24 September 2026, Anthropic announced that Claude Tag in Slack channels can use the personal connectors of the person making a request. This removes the prior restriction to admin-attached channel connectors for that person's request. It does not grant other channel members access to that person's connected account. It also does not make a channel reply private: once posted, the response is visible to everyone in that channel. The new capability is rolling out on Claude Team, with Enterprise support to follow.
What changed for a team request
An employee can ask Claude in a channel to compare a document available through their own Drive connector with work available through a shared GitHub connector. Anthropic says the personal tool activity appears under that person's account in the connected tool's log, while shared channel work remains under its service account. This is an access-control design described by the vendor, not an independent audit of every connected app, Slack retention setting or output filter.
Review mode is the practical privacy boundary
The requester can review each response before it posts, or use an auto mode that posts automatically unless Claude determines sensitive content needs review. Anthropic says Enterprise administrators will be able to require review for everyone once that rollout arrives. Treat automatic sensitivity detection as a fallible safeguard, not permission to surface client, HR, financial or regulated data into a broadly accessible channel. Pilot with review mode and a low-sensitivity account first.
Unattended routines have a different connector rule
Anthropic is explicit that personal connectors do not run unattended. Scheduled routines and work Claude starts on its own use the connectors an administrator attaches to the channel. Do not assume a teammate's permissions continue to authorize an after-hours monitoring routine or a team-wide workflow. Map every action to the human connector or shared agent identity that actually executes it.
Plans, UK availability and price checks
Claude Tag is a Slack beta for Claude Team and Enterprise customers, according to the product page. The specific personal-connector feature is rolling out first on Team; Enterprise is described as following, not already generally available for this feature. Anthropic does not state a standalone price or public API/model identifier for personal connectors. A UK buyer should confirm its signed-in Team quote, seat terms, connected-service licences, administrator controls and rollout state before treating a published plan price as a complete cost.
Run one governed pilot
Use a test Slack channel and one read-only connector with a least-privilege account. Have the requester ask a bounded question, inspect the proposed response in review mode and confirm that another member cannot call the requester's connector. Check source-system audit logs, channel membership, exports, Slack retention, connector revocation and what happens if the account loses access. Measure the accepted answer and review minutes against the current manual workflow; test any scheduled routine separately with shared credentials.
HubAI buyer verdict
The update can make Claude Tag more useful when a team question spans a personal document and a shared system without broadening raw tool access. The main risk moves to the generated answer crossing into a shared channel. Shortlist it for supervised, permission-aware collaboration only after a Team rollout check and a response-review pilot. This is not evidence of secure handling in every deployment or of measured productivity savings. Claude remains Test pending without a HubAI Score.
Evidence limits and editorial disclosure
Independent editorial coverage; not sponsored. Product and rollout statements come from Anthropic's 24 September announcement and its Claude Tag and pricing pages, checked 25 September 2026. HubAI has not independently tested the connector permissions, sensitivity screening or audit behaviour. The visible UK Google Trends top 25 did not show a directly relevant query; no search-volume claim is made. The cover is a conceptual illustration, not a product screenshot or certification claim.
HUBAI VIEWPilot one read-only request with review-before-posting, then test permissions, logs and sensitive-output handling before enabling automatic replies or shared routines.
Buyer decision signal: Team rollout · personal connectors and response review
What to verify next
1Confirm that the personal-connector capability is enabled on the intended Team workspace; do not assume Enterprise rollout is complete
2List connector scopes, channel membership, guest access and retention before connecting real data
3Use review-before-posting for the first read-only, low-sensitivity request
4Verify that other members cannot invoke a requester's personal connector and that the source log identifies the requester
5Test what content is exposed in the final channel message, including citations, snippets and follow-up questions
6Use admin-attached shared connectors for scheduled or self-started routines; audit and revoke separately
7Measure accepted answers, human review minutes and complete seat and connector costs against the manual route
Read the evidence
Capabilities, availability and prices can change. HubAI keeps analysis separate from the underlying official material.
01Anthropic: Claude Tag personal connectors in channels — 24 September 2026Open source ↗02Anthropic: Claude Tag product and Slack betaOpen source ↗03Anthropic: Claude plan pricingOpen source ↗
Products
Products
Products
Products