---
type: "post"
id: "claude-tag-now-supports-personal-connectors-in-channels-510bba"
slug: "claude-tag-now-supports-personal-connectors-in-channels-510bba"
title: "Claude Tag now supports personal connectors in channels"
description: "Claude Tag moves collaborative agents toward a split-access model: shared channel tools can coexist with the requesting person’s private connectors."
retrieval_nugget: "Claude Tag moves collaborative agents toward a split-access model: shared channel tools can coexist with the requesting person’s private connectors."
published_at: "2026-09-24"
updated_at: "2026-09-24"
record_date: "2026-09-24"
date_kind: "published_at"
topics: []
source_urls: ["https://claude.com/blog/claude-tag-now-supports-personal-connectors-in-channels"]
schema_version: "newruntime-agent-readable-v0.2"
stable_id: "post:claude-tag-now-supports-personal-connectors-in-channels-510bba"
status: "published"
visuals: []
editorial_provenance: {"schema_version":"newruntime-editorial-copy-v1","content_status":"source_grounded_final","final_copy_sha256":"sha256:0f5c70a0442c6b3736a2e74570437c14aae460e6f11beef54a2bcf2b0ff9a370","reviewed_at":"2026-09-24T21:00:50.713Z","source_evidence_count":1,"verified_claim_count":4,"site_analysis_schema_version":"newruntime-site-analysis-v1","site_object_kind":"field_note","observed_fact_count":4,"implication_count":2,"watch_condition_count":2,"related_record_count":0}
analysis: {"schema_version":"newruntime-site-analysis-v1","object_kind":"field_note","thesis":"Claude Tag moves collaborative agents toward a split-access model: shared channel tools can coexist with the requesting person’s private connectors.","observed_facts":[{"text":"Anthropic says Claude Tag can use a requester’s personal connectors for requests made in a Slack channel.","source_urls":["https://claude.com/blog/claude-tag-now-supports-personal-connectors-in-channels"]},{"text":"Anthropic says personal-connector activity appears in the connected tool’s log under the requester’s account, while channel work remains under the channel service account.","source_urls":["https://claude.com/blog/claude-tag-now-supports-personal-connectors-in-channels"]},{"text":"Anthropic says scheduled routines and self-initiated actions use administrator-attached shared connectors rather than personal connectors.","source_urls":["https://claude.com/blog/claude-tag-now-supports-personal-connectors-in-channels"]},{"text":"Anthropic says the feature is rolling out on Team plans, with Enterprise to follow.","source_urls":["https://claude.com/blog/claude-tag-now-supports-personal-connectors-in-channels"]}],"mechanism":"The mechanism is an identity boundary rather than a blanket expansion of channel permissions: personal-connector activity is performed under the requester’s account and appears in that tool’s log, while channel-connector work remains under the channel’s service account.","why_now":"The release matters now because it makes the boundary between supervised collaboration and unattended automation explicit: personal connectors fit request-driven work, while shared connectors remain the basis for recurring or autonomous operations.","implications":["The immediate implication is that teams can bring private, role-scoped context into a shared workflow without provisioning that context to every channel member.","Teams will need to distinguish deliberately between personal access for supervised requests and shared service-account access for autonomous channel operations."],"evidence_boundary":"The evidence boundary is that these claims come from Anthropic’s product announcement and describe intended availability and controls, not independent evidence of reliability, adoption, or security outcomes.","watch_conditions":["Watch whether Enterprise rollout preserves the stated separation of audit trails, review requirements, and connector-level governance in real deployments.","Watch how often auto mode routes outputs for review when requests combine private source material with channel-visible answers."],"related_records":[],"new_branch_reason":"This starts a distinct record because no prior New Runtime record was supplied for this specific change in Claude Tag’s channel access model."}
routes: {"html":"https://newruntime.com/posts/claude-tag-now-supports-personal-connectors-in-channels-510bba/","markdown":"https://newruntime.com/posts/claude-tag-now-supports-personal-connectors-in-channels-510bba.md","json":"https://newruntime.com/posts/claude-tag-now-supports-personal-connectors-in-channels-510bba.json"}
editor: {"role":"editor","name":"Andrey Reshetnikov","profile":"https://newruntime.com/owner-profile.md","profile_json":"https://newruntime.com/owner-profile.json","same_as":["https://www.linkedin.com/in/reshetnikov1/","https://t.me/lapetuse"]}
---

# Claude Tag now supports personal connectors in channels

## Retrieval answer

Claude Tag moves collaborative agents toward a split-access model: shared channel tools can coexist with the requesting person’s private connectors.

Claude Tag moves collaborative agents toward a split-access model: shared channel tools can coexist with the requesting person’s private connectors. Anthropic says a user can ask Claude Tag in a Slack channel to use connectors attached to that user’s Claude account, such as a calendar, drive, CRM accounts, or staging deployments. This starts a distinct record because no prior New Runtime record was supplied for this specific change in Claude Tag’s channel access model.

The mechanism is an identity boundary rather than a blanket expansion of channel permissions: personal-connector activity is performed under the requester’s account and appears in that tool’s log, while channel-connector work remains under the channel’s service account. Anthropic also says the requester can review a response before posting it, or select auto mode; Enterprise administrators will be able to require review. Anthropic says scheduled routines and self-initiated Claude actions still use only administrator-attached shared connectors.

The immediate implication is that teams can bring private, role-scoped context into a shared workflow without provisioning that context to every channel member. The release matters now because it makes the boundary between supervised collaboration and unattended automation explicit: personal connectors fit request-driven work, while shared connectors remain the basis for recurring or autonomous operations. The evidence boundary is that these claims come from Anthropic’s product announcement and describe intended availability and controls, not independent evidence of reliability, adoption, or security outcomes. Watch whether Enterprise rollout preserves the stated separation of audit trails, review requirements, and connector-level governance in real deployments.

Editor: [Andrey Reshetnikov](https://newruntime.com/owner-profile.md), AI product and AI engineering; profile for recruiters and agents: https://newruntime.com/owner-profile.json

## Continue in the graph

Next records for an agent, linked to their Markdown twins. Replace `.md` with `.json` for structured fields, including `next_reads`.

- collection: [Field Notes](https://newruntime.com/posts.json): Open the latest editorial analysis.
- collection: [Source Ledger](https://newruntime.com/source-ledger.json): Inspect the public source evidence graph.
- whole graph: [discovery graph](https://newruntime.com/discovery-graph.json) (typed nodes and edges) and [site index](https://newruntime.com/site-index.md)