Personal connectors in channels changedclaude-tag/concepts/personal-connectors
Nearest release: v2.1.283, published 3 hours before upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Upstream edited this page at 25 Sep 2026 22:04 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 25 Sep 2026 22:07 UTC.
Upstream edited
Recorded here
Lines+10added
Lines−3removed
From line
8
where the diff opens
First seen
10 Sep 2026
this site's first read of the page
Recorded edits6to this page, all time
### Admin controls for personal connectors
The whole hunk
from line 8, old and new numbered
/
from line 8
88
99Personal connectors are the tools you add to your own claude.ai account, like your calendar or your email. When a task you ask for in a Slack channel needs one of your own tools, Claude can offer to use your connector for it.
1010
11Connector use in channels is available to a limited number of organizations. If Claude never offers to use your connectors in a channel, connector use in channels may not be available to your organization, and the channel works with admin-attached connections as described in [how agent identity works](/docs/claude-tag/concepts/agent-identity).
11Personal connectors in channels are on for every organization on the Team plan, with nothing for an admin to set up. On the Enterprise plan, the **Personal connectors** section at [`claude.ai/admin-settings/claude-tag`](https://claude.ai/admin-settings/claude-tag) says when they turn on for your organization. A channel also keeps working with the connections an admin attached to it, as described in [how agent identity works](/docs/claude-tag/concepts/agent-identity).
1212
1313## Where your connectors apply
1414
15In organizations where connector use in channels is available, Claude can use your personal connectors for the requests you make in a channel.
15Claude can use your personal connectors for the requests you make in a channel.
1616
1717* **Approval**: Claude asks you before it starts using your connectors in a channel.
1818* **Access**: Claude works with your permissions and reaches only what your account can reach.
from line 63
6363
6464Once you approve a held result, Claude posts it in the thread where you asked.
6565
66On the Enterprise plan, an Owner can set the review rule for a scope with the **Delegated task results** setting, at [`claude.ai/admin-settings/claude-tag`](https://claude.ai/admin-settings/claude-tag) → **Claude Tag's access** → **Slack** → the scope → **Advanced** → **Delegated task results**. **Require review** removes **Allow** from the prompt and **Auto mode** from the **Home** tab, so Claude holds every result for your review. **Share without review** removes **Allow with review** from both.
66### Admin controls for personal connectors
67
68Admins manage personal connectors for the whole organization in the **Personal connectors** section at [`claude.ai/admin-settings/claude-tag`](https://claude.ai/admin-settings/claude-tag). The settings there apply to every workspace and channel.
69
70* **Require human review of every message.** On the Enterprise plan, an admin can turn this switch on so that Claude holds every result for the requester's review, not only the ones the sensitive-content check flags. With it on, the prompt no longer offers **Allow** and the **Home** tab no longer offers **Auto mode**. On the Team plan, results the check doesn't flag post without review.
71* **Sensitive information requiring review.** Lists what the check looks for. An Owner can add topics of your own under **Additional topics**, for example "Board meeting notes are confidential", and Claude holds results that touch them.
72
73There is no setting that turns personal connectors in channels off for an organization. To keep a service out of channels entirely, manage the connector itself in your organization's [connector settings](/docs/connectors/getting-started).
6774
6875### Stop connector use
6976
No line in this hunk matches that.