One read of Claude Documentationclaude-docs-20261013T200705Z
2 pages moved out of 265 read.
Pages moved
2
significant first
Pages read
265
in this capture
Captured
20:07 UTC
Corpus hash
1f6eb9a26b1d
corpus-hash
What this read moved
1-2 of 2claude-tag/admins/restrict-access Changed · +42 / -29 lines
#### Turn Claude on in Slack Connect channels #### When Claude does not answer in a Slack Connect channel
from line 218
218218
219219### Slack Connect channels
220220
221A Slack Connect channel is a channel your Slack workspace shares with another company. The [**How should Claude work in channels with guests**](#restrict-guest-channels) setting decides whether Claude answers in one:
221A Slack Connect channel is a channel your Slack workspace shares with another company. The [**How should Claude work in channels with guests**](#restrict-guest-channels) setting, the same one that governs channels that include guests, decides whether Claude answers in one:
222222
223223* **Restrict** (default): Claude doesn't answer, and posts no notice when someone mentions it.
224* **Channel only** or **Full access**: Claude answers with the [limited access it has in a Slack Connect channel](#what-access-claude-has-in-a-slack-connect-channel). **Full access** gives Claude no more access there than **Channel only**.
224* **Channel only** or **Full access**: Claude answers. Access in a Slack Connect channel is capped at channel-only access, so **Full access** gives Claude the same [limited access](#what-access-claude-has-in-a-slack-connect-channel) there as **Channel only**.
225225
226To turn Claude on in Slack Connect channels, go to [**Claude's access > Channels**](https://claude.ai/admin-settings/claude-tag?access=channels), open the **Slack** page, a workspace's page, or one channel's page, and on its **Advanced** tab set **How should Claude work in channels with guests** to **Channel only**. An Owner or a [Claude Tag admin](#delegate-claude-tag-administration) can make this change. The same value applies to the scope's channels that include guests, so a scope already set to **Channel only** or **Full access** for guests answers in its Slack Connect channels too, except in a channel with its own value. A value on the channel's own page wins over the workspace's, and the workspace's wins over the **Slack** page.
226#### Turn Claude on in Slack Connect channels
227227
228When someone who isn't a full member of your workspace adds Claude to a Slack Connect channel with no value of its own, Claude sets that channel's page to **Restrict**. That includes someone from the other company, a guest, a bot or workflow, and an [auto-join pattern](#block-or-auto-join-channels-by-name). To let Claude answer there, change the value on the channel's page.
228To turn Claude on in Slack Connect channels, go to [**Claude's access > Channels**](https://claude.ai/admin-settings/claude-tag?access=channels), open the **Slack** page, a workspace's page, or one channel's page, and on its **Advanced** tab set **How should Claude work in channels with guests** to **Channel only**. An Owner or a [Claude Tag admin](#delegate-claude-tag-administration) can make this change.
229229
230Claude also doesn't answer in a Slack Connect channel in these cases, and posts a notice only in a thread from before the channel was shared:
230The same value applies to the scope's channels that include guests, so a scope already set to **Channel only** or **Full access** for guests answers in its Slack Connect channels too.
231231
232* **Claude Tag turned off.** The [**Enable Claude Tag** switch](/docs/claude-tag/admins/workspaces#turn-claude-tag-on-or-off-and-set-the-version-for-a-scope) that covers the channel is off.
233* **Blocked name.** The channel's name matches one of the [**Blocked channel patterns**](#block-or-auto-join-channels-by-name).
234* **Legacy version.** The scope's [Claude Tag version](/docs/claude-tag/admins/workspaces#turn-claude-tag-on-or-off-and-set-the-version-for-a-scope) is **Legacy**.
235* **Enterprise Grid organization-level installs.** Claude is installed for your whole Enterprise Grid organization rather than per workspace, and none of your own workspaces hosts the channel.
236* **Threads from before the channel was shared.** Claude doesn't continue a thread it was already working in before the channel was shared. A mention there gets the notice "This channel is now shared with another organization through Slack Connect, so this thread's earlier session can't continue here," and a new thread works.
237* **Messages from the other company's Claude.** Claude doesn't reply to the other company's Claude. If the other company also uses Claude, each company's settings decide only whether its own Claude answers.
232When someone who isn't a full member of your workspace adds Claude to a Slack Connect channel with no value of its own, Claude sets that channel's page to **Restrict**. That includes someone from the other company, a guest, a bot or workflow, and an [auto-join pattern](#block-or-auto-join-channels-by-name). To let Claude answer there, open the channel's page under [**Claude's access > Channels**](https://claude.ai/admin-settings/claude-tag?access=channels) and on its **Advanced** tab set **How should Claude work in channels with guests** to **Channel only**.
238233
239234#### What access Claude has in a Slack Connect channel
240235
241When Claude answers in a Slack Connect channel, it follows the channel's own instructions and has:
236Claude answers in a Slack Connect channel where [**How should Claude work in channels with guests**](#restrict-guest-channels) is **Channel only** or **Full access**. Its access there is capped at channel-only access under either value. Claude follows the channel's own instructions, and [bundles](/docs/claude-tag/admins/attach-to-scope) apply there according to how each one is attached:
242237
243* No [bundles](/docs/claude-tag/admins/attach-to-scope) or connections inherited from the workspace or the **Slack** page, and none attached by a [channel rule](/docs/claude-tag/admins/attach-to-scope#attach-a-bundle-to-channels-by-name), except a bundle attached specifically for Slack Connect channels. A bundle [attached directly to the channel](/docs/claude-tag/admins/attach-to-scope#attach-to-a-channel) still applies, whether it was attached before or after the channel was shared and whoever attached it, unless it's set to apply only in channels with guests. Claude can use the connectors in that bundle for anyone it answers there, including the other company's people.
238* **Attached directly to the channel.** The bundle applies whether it was [attached to the channel](/docs/claude-tag/admins/attach-to-scope#attach-to-a-channel) before or after the channel was shared and whoever attached it, unless it's set to apply only in channels with guests.
239* **Inherited, or attached by a channel rule.** A bundle inherited from the workspace or the **Slack** page, or attached by a [channel rule](/docs/claude-tag/admins/attach-to-scope#attach-a-bundle-to-channels-by-name), doesn't apply, except a bundle attached specifically for Slack Connect channels.
240
241When a bundle applies there, Claude can use the bundle's connectors for anyone it answers in the channel, including the other company's people.
242
243<Warning>Treat the channel's instructions, and the connectors in its bundles, as available to the other company. Before you turn Claude on in a Slack Connect channel, or share a channel where it's already on, open the channel's page under [**Claude's access > Channels**](https://claude.ai/admin-settings/claude-tag?access=channels), check its bundles, and [remove the channel from any bundle](/docs/claude-tag/admins/attach-to-scope#choose-where-a-bundle-applies) you don't want used there.</Warning>
244
245When it answers there, Claude also has:
246
247* No connections inherited from the workspace or the **Slack** page.
244248* No instructions set on the workspace or on the **Slack** page.
245249* No memory, skills, or repositories.
246250* No [environment set on the scope](/docs/claude-tag/admins/customize#configure-the-environment-for-a-scope). The session runs on the standard environment.
247251
248Treat the channel's instructions, and the connectors in its bundles, as available to the other company. Before you turn Claude on in a Slack Connect channel, or share a channel where it's already on, check the bundles on the channel's page and [remove the channel from any bundle](/docs/claude-tag/admins/attach-to-scope#choose-where-a-bundle-applies) you don't want used there.
249
250252In a Slack Connect channel, Claude also doesn't search your workspace, look up people or channels, read other channels, publish [artifacts](/docs/claude-tag/concepts/security-and-data#artifact-visibility), or set up [routines](/docs/claude-tag/users/proactivity). Routines set up in the channel before it was shared don't run there.
251253
252254#### Who can use Claude in a Slack Connect channel
from line 255
253255
254256People from the other company can talk to Claude by mentioning `@Claude` or by replying in a thread Claude is part of, and Claude answers them. Everyone in the channel, including the other company's people, can read what Claude posts.
255257
256* **Limit Claude to your organization.** Go to [**Claude's access > Channels > Slack**](https://claude.ai/admin-settings/claude-tag/channels/slack), open the **Advanced** tab, and turn on **Restrict to your organization** (**Restrict to roles with Claude Tag access** on Enterprise). Someone from the other company who then mentions `@Claude` to start a conversation gets a message only they can see, and in an existing thread Claude declines their request. The toggle applies to channels and DMs alike, so members of your workspace without a Claude account (on Enterprise, without a role that grants **Claude Tag in Slack**) lose access too.
258* **Limit Claude to your organization.** Go to [**Claude's access > Channels > Slack**](https://claude.ai/admin-settings/claude-tag/channels/slack), open the **Advanced** tab, and turn on the **Restrict to your organization** toggle (**Restrict to roles with Claude Tag access** on Enterprise). Someone from the other company who then mentions `@Claude` to start a conversation gets a message only they can see, and in an existing thread Claude declines their request. The toggle applies to channels and DMs alike, so members of your workspace without a Claude account (on Enterprise, without a role that grants **Claude Tag in Slack**) lose access too.
257259* **Automatic replies.** While the channel's [**Respond automatically**](/docs/claude-tag/users/when-claude-responds#turn-automatic-replies-on-or-off) setting is on, messages from your members that don't mention Claude reach it, and Claude may reply to some of them on its own. Outside the threads Claude is part of, messages from the other company's people that don't mention Claude reach it only as context, not as requests.
258260* **Commands.** Your organization's members can send `@Claude` followed by `!help`, `!mute`, `!unmute`, `!restart`, or `!fast`. People from the other company can use only `!help`, and other [commands](/docs/claude-tag/users/commands) do nothing there.
261
262#### When Claude does not answer in a Slack Connect channel
263
264After you [turn Claude on in Slack Connect channels](#turn-claude-on-in-slack-connect-channels), Claude still doesn't answer there in these cases, and posts a notice only in a thread from before the channel was shared:
265
266* **Claude Tag turned off.** The [**Enable Claude Tag** switch](/docs/claude-tag/admins/workspaces#turn-claude-tag-on-or-off-and-set-the-version-for-a-scope) that covers the channel is off.
267* **Blocked name.** The channel's name matches one of the [**Blocked channel patterns**](#block-or-auto-join-channels-by-name).
268* **Legacy version.** The scope's [Claude Tag version](/docs/claude-tag/admins/workspaces#turn-claude-tag-on-or-off-and-set-the-version-for-a-scope) is **Legacy**.
269* **Enterprise Grid organization-level installs.** Claude is installed for your whole Enterprise Grid organization rather than per workspace, and none of your own workspaces hosts the channel.
270* **Threads from before the channel was shared.** Claude doesn't continue a thread it was already working in before the channel was shared. A mention there gets the notice "This channel is now shared with another organization through Slack Connect, so this thread's earlier session can't continue here," and a new thread works.
271* **Messages from the other company's Claude.** Claude doesn't reply to the other company's Claude. If the other company also uses Claude, each company's settings decide only whether its own Claude answers.
259272
260273### Channels shared across workspaces in your Enterprise Grid
261274
third-party/claude-desktop/feature-matrix Changed · +88 / -71 lines
## Key differences from Claude Enterprise ## Features in Claude Desktop on 3P ## Good to know about Claude Desktop on 3P ## Key differences ## User features ## Admin features
from line 2
22
33> Feature comparison between Claude Enterprise and Claude Desktop on third-party (3P)
44
5The tables below compare the feature set of Claude Desktop on third-party (3P) to Claude Enterprise.
5Claude Desktop on third-party (3P) is a deployment mode of Claude Desktop that routes all model inference through [a provider you configure](/docs/third-party/claude-desktop/overview). Pricing is token-based consumption billed by your cloud provider, with no seat licensing.
66
7## Key differences
7## Key differences from Claude Enterprise
88
9**Configuration.** Both are administered from the web-based [admin console](/docs/third-party/claude-desktop/admin-console) in **Organization settings** on claude.ai. Claude Desktop on 3P can also be configured through [MDM](/docs/third-party/claude-desktop/mdm) (Jamf, Intune, Group Policy) or a [bootstrap server](/docs/third-party/claude-desktop/bootstrap).
9<div className="feature-compare">
10 | Feature | Claude Enterprise | Claude Desktop on 3P |
11 | - | :-: | :-: |
12 | [Connect to your cloud provider for inference](/docs/third-party/claude-desktop/configuration#connection) | <Icon icon="xmark" color="#9E9E9E" /> No | <Icon icon="circle-check" iconType="solid" /> **Yes** |
13 | [Data residency in multiple regions](/docs/third-party/claude-desktop/overview#data-residency-and-international-deployment) | <Icon icon="xmark" color="#9E9E9E" /> No | <Icon icon="circle-check" iconType="solid" /> **Yes**, depending on provider |
14 | [Run inference outside Anthropic's cloud](/docs/third-party/claude-desktop/overview#data-handling-by-provider) | <Icon icon="xmark" color="#9E9E9E" /> No | <Icon icon="circle-check" iconType="solid" /> **Yes**, depending on provider |
15 | Mobile and claude.ai web-based access | <Icon icon="circle-check" iconType="solid" /> **Yes** | <Icon icon="xmark" color="#9E9E9E" /> No |
16 | Sessions in Anthropic's cloud | <Icon icon="circle-check" iconType="solid" /> **Yes** | <Icon icon="xmark" color="#9E9E9E" /> No |
17 | Sharing between users | <Icon icon="circle-check" iconType="solid" /> **Yes** | <Icon icon="xmark" color="#9E9E9E" /> No |
18 | Voice mode | <Icon icon="circle-check" iconType="solid" /> **Yes** | <Icon icon="xmark" color="#9E9E9E" /> No |
19 | Claude Security and [Claude Tag](/docs/claude-tag/overview) | <Icon icon="circle-check" iconType="solid" /> **Yes** | <Icon icon="xmark" color="#9E9E9E" /> No |
20</div>
1021
11**Telemetry.** Claude Desktop on 3P sends usage and debugging metrics only, and these can be fully disabled via managed configuration. Claude Enterprise does not offer telemetry toggles. See [Telemetry and egress](/docs/third-party/claude-desktop/telemetry).
22## Features in Claude Desktop on 3P
1223
13**Inference.** Claude Desktop on 3P routes all inference through the provider you configure, and data handling at the inference endpoint depends on that provider. For Google Cloud's Agent Platform and Amazon Bedrock, data handling is governed by Google Cloud and Amazon Bedrock respectively. For Microsoft Foundry, Anthropic operates the Claude models and handles conversation data as an independent processor for Microsoft. See [Data handling by provider](/docs/third-party/claude-desktop/overview#data-handling-by-provider) on the Overview page for each provider's data path.
24Some features have limits or need setup, described in [Good to know about Claude Desktop on 3P](#good-to-know-about-claude-desktop-on-3p).
1425
15**Pricing.** Claude Desktop on 3P is token-based consumption billed by your cloud provider, with no seat licensing.
26Claude Desktop on 3P is administered from the web-based [admin console](/docs/third-party/claude-desktop/admin-console), and can also be configured through [MDM](/docs/third-party/claude-desktop/mdm) or a [bootstrap server](/docs/third-party/claude-desktop/bootstrap).
1627
17**Sharing between users.** In Claude Desktop on 3P, users can't share chats, projects, artifacts, skills, or plugins with each other from the app. Administrators can [distribute skills and plugins](/docs/third-party/claude-desktop/extensions) to users.
28<Card title="Everyday work" icon="briefcase" color="#737373" horizontal>
29 <div className="feature-chips not-prose">
30 * [Chat](/docs/third-party/claude-desktop/chat)
31 * [Cowork](/docs/third-party/claude-desktop/configuration#coworktabenabled)
32 * Projects
33 * Artifacts
34 * [Memory](/docs/third-party/claude-desktop/data-storage#memory)
35 * [Scheduled tasks](/docs/third-party/claude-desktop/configuration#scheduledtasksenabled)
36 * [Code execution for analysis](/docs/third-party/claude-desktop/chat#advanced-file-analysis)
37 * [File access, upload, and export](/docs/third-party/claude-desktop/local-access)
38 * Global languages
39 * [Automatically approve in Cowork](/docs/third-party/claude-desktop/configuration#automodeenabled)
40 </div>
41</Card>
1842
19**Remote sessions.** In Claude Desktop on 3P, users can't run sessions remotely, on Anthropic's or another cloud, except [Code sessions over SSH](/docs/third-party/claude-desktop/ssh-remote-sessions). All other sessions are local, and the device must be awake to run long processes and scheduled tasks. If a scheduled task is missed because the machine is asleep, it runs when the machine wakes up.
43<Card title="Web and browser" icon="globe" color="#737373" horizontal>
44 <div className="feature-chips not-prose">
45 * [Built-in browser](/docs/third-party/claude-desktop/browser#built-in-browser)
46 * [Web search](/docs/third-party/claude-desktop/web-tools#web-search)
47 * [Claude in Chrome](/docs/third-party/claude-desktop/browser#claude-in-chrome)
48 </div>
49</Card>
2050
21**Features not available in 3P.** Features marked with — are absent from the UI. Users see a clean interface without error states for unavailable features.
51<Card title="Connectors and extensions" icon="plug" color="#737373" horizontal>
52 <div className="feature-chips not-prose">
53 * [Microsoft 365](/docs/third-party/claude-desktop/connectors-m365) and [GitHub](/docs/third-party/claude-desktop/connectors-github) connectors
54 * [Local MCP](/docs/third-party/claude-desktop/extensions#user-extensions)
55 * [Remote MCP](/docs/third-party/claude-desktop/extensions#managed-mcp-servers-admin)
56 * [Skills, plugins, and hooks](/docs/third-party/claude-desktop/extensions)
57 * [Plugin marketplaces](/docs/third-party/claude-desktop/extensions#plugin-marketplaces-admin)
58 </div>
59</Card>
2260
23## User features
61<Card title="Code" icon="code" color="#737373" horizontal>
62 <div className="feature-chips not-prose">
63 * [Code](/docs/third-party/claude-desktop/code)
64 * [Auto mode in Code](/docs/third-party/claude-desktop/configuration#automodeenabled)
65 * [SSH remote Code sessions](/docs/third-party/claude-desktop/ssh-remote-sessions)
66 </div>
67</Card>
2468
25| Feature | Claude Enterprise | Claude Desktop on 3P |
26| - | :-: | :-: |
27| Chat | ✓ | ✓ |
28| Cowork | ✓ | ✓ |
29| Code | ✓ | ✓ |
30| Auto mode (Code) | ✓ | ✓ |
31| [SSH remote Code sessions](/docs/third-party/claude-desktop/ssh-remote-sessions) | ✓ | ✓ |
32| Sessions in Anthropic's cloud | ✓ | — |
33| Automatically approve (Cowork) | — ¶ | ✓ Δ |
34| Skip all approvals (Cowork) | — ¶ | — |
35| Projects | ✓ | ✓ |
36| Code execution for analysis | ✓ | ✓ |
37| Web search | ✓ | ✓ § |
38| [Built-in browser](/docs/third-party/claude-desktop/browser) | ✓ | ✓ |
39| File access, upload, and export | ✓ | ✓ |
40| Local MCP | ✓ | ✓ |
41| Remote MCP | ✓ | ✓ |
42| [Microsoft 365](/docs/third-party/claude-desktop/connectors-m365) and [GitHub](/docs/third-party/claude-desktop/connectors-github) connectors | ✓ | ✓ |
43| Skills, plugins, and hooks | ✓ | ✓ |
44| Artifacts | ✓ | ✓ |
45| Memory | ✓ | ✓ † |
46| Scheduled tasks | ✓ | ✓ |
47| Global languages | ✓ | ✓ |
48| Sharing between users | ✓ | — |
49| Plugin marketplaces | ✓ | ✓ |
50| Mobile | ✓ | — |
51| claude.ai web-based access | ✓ | — |
52| Voice mode | ✓ | — |
53| [Claude in Chrome](/docs/third-party/claude-desktop/browser#claude-in-chrome) | ✓ | ✓ ‖ |
54| Claude Design | ✓ | — |
55| Claude Security | ✓ | — |
56| Claude Tag | ✓ | — |
57| Computer use | — | — |
69<Card title="Administration" icon="sliders" color="#737373" horizontal>
70 <div className="feature-chips not-prose">
71 * [Admin console](/docs/third-party/claude-desktop/admin-console)
72 * [Endpoint or gateway configuration](/docs/third-party/claude-desktop/configuration#connection)
73 * [Skills, hooks, and plugins distribution](/docs/third-party/claude-desktop/extensions#organization-plugins-admin)
74 * [MCP server allowlist](/docs/third-party/claude-desktop/extensions#controlling-user-extensions)
75 * [Feature toggles](/docs/third-party/claude-desktop/configuration#capabilities)
76 * [Auto-updates](/docs/third-party/claude-desktop/installation#updates)
77 * [Per-user usage caps](/docs/third-party/claude-desktop/configuration#inferencemaxtokensperwindow)
78 * [User management via UI](/docs/third-party/claude-desktop/admin-console#connect-your-identity-provider)
79 * [RBAC](/docs/third-party/claude-desktop/admin-console#per-group-permission-policies)
80 </div>
81</Card>
5882
59§ Amazon Bedrock deployments and gateways that do not forward Anthropic server tools need a web search provider configured first; see [Web search options](/docs/third-party/claude-desktop/web-tools#web-search-options).
83<Card title="Monitoring and retention" icon="chart-line" color="#737373" horizontal>
84 <div className="feature-chips not-prose">
85 * [OpenTelemetry export](/docs/third-party/claude-desktop/telemetry#sending-telemetry-to-your-own-collector)
86 * [Turning off telemetry](/docs/third-party/claude-desktop/telemetry#telemetry-categories)
87 * [Data retention policies](/docs/third-party/claude-desktop/data-storage#automatic-deletion-of-idle-sessions)
88 </div>
89</Card>
6090
61† Memory in Claude Desktop on 3P is stored on the device, not on Anthropic infrastructure. Users can review, delete, or pause it under **Settings → Cowork → Memory**; see [Memory](/docs/third-party/claude-desktop/data-storage#memory). Chat-history search and nightly summary generation are not available in Chat on 3P.
91## Good to know about Claude Desktop on 3P
6292
63¶ Cowork's Automatically approve and Skip all approvals modes are not available for Claude Enterprise organizations.
64
65Δ Offered when an administrator sets [`autoModeEnabled`](/docs/third-party/claude-desktop/configuration#automodeenabled) to `true`.
66
67‖ Claude in Chrome works with Claude Desktop on 3P only in organizations managed from the [Enterprise Admin Console](/docs/third-party/claude-desktop/admin-console).
68
69## Admin features
70
71| Feature | Claude Enterprise | Claude Desktop on 3P |
72| - | :-: | :-: |
73| Endpoint / gateway configuration | — | ✓ |
74| Skills, hooks, and plugins distribution | ✓ | ✓ |
75| MCP server allowlist | ✓ | ✓ |
76| Feature toggles (web search, local MCP, etc.) | ✓ | ✓ |
77| Auto-updates | ✓ | ✓ |
78| Per-user usage caps | ✓ | ✓ |
79| [Data retention policies](/docs/third-party/claude-desktop/data-storage#automatic-deletion-of-idle-sessions) | ✓ | ✓ |
80| Compliance API | ✓ | — ‡ |
81| Analytics API | ✓ | — ‡ |
82| OpenTelemetry export | ✓ | ✓ |
83| User management via UI | ✓ | ✓ ◊ |
84| RBAC | ✓ | ✓ ◊ |
85
86‡ Many of these capabilities can be achieved via OpenTelemetry export to your own collector. See [Monitoring](/docs/cowork/monitoring).
87
88◊ With the [Enterprise Admin Console](/docs/third-party/claude-desktop/admin-console), administrators add users and groups, connect single sign-on and SCIM, assign administrator roles, and set per-group permission policies from **Organization settings** on claude.ai. Deployments configured through MDM or a bootstrap server manage access through those channels.
93<Accordion title="Notes on setup, limits, monitoring, and data handling">
94 | Topic | What to know |
95 | - | - |
96 | Sessions and scheduled tasks | Sessions are local, except [Code sessions over SSH](/docs/third-party/claude-desktop/ssh-remote-sessions), and the device must be awake to run long processes and scheduled tasks. |
97 | Memory | [Memory](/docs/third-party/claude-desktop/data-storage#memory) in Claude Desktop on 3P is stored on the device, not on Anthropic infrastructure. Chat-history search and nightly summary generation are not available in Chat on 3P. |
98 | Web search | Amazon Bedrock deployments and gateways that do not forward Anthropic server tools need a [web search provider](/docs/third-party/claude-desktop/web-tools#web-search-options) configured first. |
99 | Claude in Chrome | Claude in Chrome works with Claude Desktop on 3P only in organizations managed from the [Enterprise Admin Console](/docs/third-party/claude-desktop/admin-console). |
100 | Automatically approve in Cowork | Cowork offers the **Automatically approve** mode when an administrator sets [`autoModeEnabled`](/docs/third-party/claude-desktop/configuration#automodeenabled) to `true`. |
101 | User management via UI and RBAC | With the [Enterprise Admin Console](/docs/third-party/claude-desktop/admin-console), administrators add users and groups, connect single sign-on and SCIM, assign administrator roles, and set per-group permission policies from **Organization settings** on claude.ai. Deployments configured through MDM or a bootstrap server manage access through those channels. |
102 | Monitoring | Many capabilities of the Compliance API and Analytics API can be achieved via [OpenTelemetry export](/docs/third-party/claude-desktop/telemetry#sending-telemetry-to-your-own-collector) to your own collector. |
103 | Telemetry | Claude Desktop on 3P sends [crash reports and product analytics](/docs/third-party/claude-desktop/telemetry#telemetry-categories) to Anthropic by default. This telemetry contains no prompt or response content, and you can fully disable it via managed configuration. |
104 | Data handling | [Data handling](/docs/third-party/claude-desktop/overview#data-handling-by-provider) at the inference endpoint depends on the provider you configure. For Google Cloud's Agent Platform and Amazon Bedrock, data handling is governed by Google Cloud and Amazon Bedrock respectively. For Microsoft Foundry, Anthropic operates the Claude models and handles conversation data as an independent processor for Microsoft. For the Anthropic API, Anthropic processes conversation data under your Anthropic agreement, as described on the [Claude API](/docs/third-party/claude-desktop/claude-api) page. |
105</Accordion>
89106