Skip to main content

Use Claude Cowork on Team and Enterprise plans

Updated today

This article explains important limitations and considerations for Team and Enterprise organizations using Claude Cowork.

Availability

Claude Cowork is available as a research preview for paid plans (Pro, Max, Team, Enterprise) on:

  • Claude Desktop for macOS

  • Claude Desktop for Windows

    • Windows users: Cowork requires the latest version of Claude for Windows. Download or update at claude.com/download.


Admin controls

Claude Cowork will be on by default when the research preview launches, but organization owners can manually disable it.

How to enable or disable Cowork:

  1. Log in to your Team or Enterprise organization as an Owner or Primary Owner.

  2. Locate the Cowork toggle.

  3. Toggle off to disable Cowork for all users in your organization.

Note: This is an organization-wide setting. Granular controls by user or role are not currently available.

Plugins

Plugins are included with Cowork and controlled by the same admin toggle—there's no separate setting to manage plugin access within Cowork.

For details on what members can do with plugins, see Use plugins in Cowork.


Projects

Projects in Cowork let users organize tasks into dedicated workspaces with their own files, links, instructions, and memory. Projects are available to all Cowork users. There are no separate admin controls for projects, so owners cannot restrict project creation at the organization level at this time.

Project data (tasks and memory) is stored locally on each user's computer, consistent with how other Cowork data is handled. For full details, see Organize your tasks with projects in Cowork.


Manage plugins for your organization

Owners can create plugin marketplaces to distribute curated plugins across their organization. This gives you control over which plugins your team members see and use in Cowork.

  • Installed by default — Automatically added for everyone in your organization. Members can uninstall if they choose.

  • Available — Appears in the plugin catalog for members to install on their own.

  • Required — Automatically installed for all members. Members cannot uninstall it.

  • Not available — Hidden from the catalog. Useful for staging or deprecating plugins.

On Enterprise plans, admins can also override these preferences for specific groups—for example, auto-installing a plugin for one team while hiding it from everyone else. For details, see Manage Cowork plugins for your organization.


Company branding

Cowork now surfaces your organization's branding, including a redesigned home screen tailored to your team. Team and Enterprise owners can configure branding within Organization settings.


Compliance and monitoring limitations

Cowork currently lacks several enterprise monitoring and compliance capabilities. These limitations are important to understand before enabling Cowork for your organization.

No audit logging or data exports

Cowork activity is not captured in:

  • Audit Logs

  • Compliance API

  • Data Exports

If your organization requires audit trails for compliance purposes, do not enable Cowork for regulated workloads.

OpenTelemetry support

Team and Enterprise owners can stream Cowork events to your SIEM and observability tools through OpenTelemetry. This gives security teams visibility into tool calls, file access, human approval decisions, and more—though it doesn't replace audit logging for compliance purposes. For setup, supported events, and security considerations, see Monitor Cowork activity with OpenTelemetry.

You can also refer to Monitoring in our Claude Docs for more information.

Cowork architecture controls

Enterprise admins can configure how Cowork's sandbox runs on member devices, including the option to require that all Cowork activity execute inside a virtual machine. For details, see Configure Claude Cowork's sandbox for your Enterprise organization.

Local conversation storage

Cowork stores conversation history locally on users' computers. This data is not subject to Anthropic's standard data retention policies and cannot be centrally managed or exported by admins.

Access controls

The Cowork toggle is organization-wide — either all members have access or none do. On Enterprise plans, admins who need per-team control can use groups and custom roles to selectively enable Cowork for specific users or teams. Team plans don't have access to these controls, so Cowork remains all-or-nothing.

Within Cowork, admins have more granular control over plugins. You can set per-plugin installation preferences to control which plugins are auto-installed, available for self-service, or hidden from your organization's catalog. On Enterprise plans, these preferences can also be customized per group. See Manage plugins for your organization for details.


Security considerations

Prompt injection risks

Cowork has unique risks due to its agentic nature and internet access. While we've implemented safety measures including model training and content classifiers, the risk of prompt injection attacks is non-zero.

Users should:

  • Avoid granting access to files with sensitive information

  • Monitor Claude for suspicious actions

  • Limit browser and web access to trusted sources

  • Report suspicious behavior immediately

For detailed guidance, see Use Cowork safely.

Network access

Cowork respects your organization's current network egress permissions. Review your network access settings in Organization settings > Capabilities under Code execution before enabling Cowork.

Important: Network egress permissions don't apply to the web search tool or MCPs, including Claude in Chrome. Team or Enterprise plan owners can turn off web search for Cowork and Chat in Organization settings > Capabilities, or Claude in Chrome via Organization settings > Claude in Chrome.

Did this answer your question?