Anthropic has made the unified Claude chat-and-Cowork experience generally available to Claude Enterprise customers. Instead of choosing a separate Chat or Cowork mode before starting, employees can begin with a message and let Claude move into more involved work when the task calls for it. The unified experience is available on web, desktop, and mobile when an organization enables it.
For organizations evaluating Claude Cowork Enterprise, the key change is not simply a redesigned interface. It is a different way to hand off work: a conversation can start with a question, continue into file handling or code execution in a cloud session, and return results in that same conversation for review. Access, model choices, network permissions, approvals, and spending remain important parts of an enterprise rollout. ([claude.com](https://claude.com/es/resources/articles/unified-claude-enterprise))
What the unified Claude experience changes
Previously, employees had to decide whether a task belonged in chat or Cowork before they began. With the unified experience, conversations start as chat. A straightforward question can stay a straightforward exchange; if the work requires more steps, such as running code or working with files, Claude can continue the same conversation in a Cowork cloud session. It then brings the completed work back for the user to review.
This can make tasks that combine discussion and execution feel more continuous. For example, a team member might ask Claude to summarize a collection of documents, compare figures in supplied files, or prepare a draft deliverable. The employee can describe the desired outcome and provide the relevant inputs, rather than first selecting a product mode. This is a workflow illustration, not a guarantee that Claude will complete every task without supervision: users should check important analysis and files before relying on them.
Cloud sessions are managed by Anthropic and run in isolated virtual machines. A task can continue after the user closes a laptop, and the conversation can be picked up on web, desktop, or mobile. Claude’s chat history, projects, connectors, skills, and plugins carry over to the unified experience. Enterprise admins can also optionally allow members to link a computer through the desktop app for access to local folders, local MCP servers, and applications, subject to the organization’s remote-control and device policies. ([claude.com](https://claude.com/es/resources/articles/unified-claude-enterprise))
Why the change matters to Enterprise teams
The user-facing benefit is a simpler starting point. Employees do not need to understand which interface is best for every request before they can get help. Teams can move from a short question to a longer, multi-step task within a single conversation, and switch devices to check progress or results.
For admins, the unified experience brings chat and cloud-based Cowork work under a single capability that can be managed across the organization and through custom roles. That can support staged rollouts: administrators can enable access for a pilot group, collect feedback, and expand access in waves. Existing identity controls, including organization sign-in and SCIM provisioning, continue to apply; the new experience does not create a separate sign-in. ([support.claude.com](https://support.claude.com/en/articles/17444462-set-up-and-manage-the-new-unified-claude-experience-for-your-enterprise-organization))
Unification does not mean every Claude product becomes the same thing. The announcement concerns Chat and Cowork. Claude Code and Claude in Chrome remain separate products for reporting purposes, for example. Teams should treat the unified experience as one place to start chat and delegate supported agentic work—not as a replacement for every Claude tool or every existing company workflow. ([support.claude.com](https://support.claude.com/en/articles/17444462-set-up-and-manage-the-new-unified-claude-experience-for-your-enterprise-organization))
How Enterprise admins can enable it
The feature is generally available, but an organization may still need to enable it. Anthropic’s Enterprise setup documentation says the setting is called Chat and Cowork unified and is managed in Organization settings > Capabilities. For an existing organization, an Owner or Primary Owner can turn it on there. The organization also needs both the Chat capability and cloud code execution and file creation enabled. Cowork or Cowork in the cloud does not need to be separately enabled for the unified experience. ([support.claude.com](https://support.claude.com/en/articles/17444462-set-up-and-manage-the-new-unified-claude-experience-for-your-enterprise-organization))
When the organization-wide setting is on, members with the standard User, Admin, Owner, or Primary Owner roles receive access. For custom roles, the capability must be included in the role. Admins who want to restrict access should review custom-role capabilities before enabling the organization setting: Anthropic notes that new roles start with all capabilities, including the unified one. Role membership can also be synchronized through SCIM, which can help teams grant access in planned groups.
A practical rollout sequence is to review the security and procurement requirements, test in a sandbox or with a small pilot group, and check network-egress, connector, sharing, and remote-control policies before broadening availability. Anthropic recommends monitoring usage and gathering feedback for two to four weeks before expanding in waves. Members may need to refresh the Claude app if the updated experience does not appear immediately. ([support.claude.com](https://support.claude.com/en/articles/17444462-set-up-and-manage-the-new-unified-claude-experience-for-your-enterprise-organization))
Access controls, security, and oversight
Admins can use role-based capabilities to decide which members may use the unified experience. Other controls still matter once access is granted. For cloud code execution, Enterprise network egress is off by default; administrators can configure allowed destinations, such as package managers, a custom list of domains, or all domains. Connector policies can block connectors, require approval, or restrict their use by role. Admin settings can also determine whether users may approve actions automatically or skip approvals, and whether chats or cloud sessions can be shared. ([support.claude.com](https://support.claude.com/en/articles/17444462-set-up-and-manage-the-new-unified-claude-experience-for-your-enterprise-organization))
These controls are relevant because an agentic task may involve actions beyond producing a text answer. Before rollout, security teams should decide what external network access is appropriate, which connectors employees need, and what approval behavior is acceptable for the organization’s data and workflows. If local computer access is enabled, device-management policies should also be reviewed. Cloud execution and optional local access have different boundaries; admins should not assume that one setting governs every kind of access.
Anthropic’s announcement says the cloud sessions use isolated virtual machines, that network egress is off by default for Enterprise, and that connector credentials are kept outside the sandbox. It also says data is encrypted in transit and at rest and is not used for model training by default. These are useful parts of the vendor’s description, but organizations should still complete their own security and compliance review against their requirements and configuration. ([claude.com](https://claude.com/es/resources/articles/unified-claude-enterprise))
Usage management and Efficient mode
Claude Enterprise pricing remains usage-based. Longer tasks involving code execution, file work, or multiple steps can use more than a quick chat, so adoption planning should include cost monitoring. Existing spend controls apply, and admins can set spend limits at the organization, group, and member levels. Usage analytics report activity under a separate Chat and Cowork unified category for members who have access to the unified experience. When comparing totals over time, admins should account for this new reporting category so that activity moved out of separate Chat or Cowork lines is not mistaken for a decline in usage. ([claude.com](https://claude.com/es/resources/articles/unified-claude-enterprise))
The new Efficient mode is a model-access option for the unified experience. When enabled, members can use only Sonnet and Haiku models in that experience, and new sessions start on Claude Sonnet 5.5 at low effort. Owners can enable it organization-wide on the Models page or for selected custom roles in each role’s Models tab. Anthropic says other products are not affected and that the default model and effort level may change as lower-cost models become available. Efficient mode restricts model options; it does not replace spend limits or usage monitoring. ([support.claude.com](https://support.claude.com/en/articles/17444462-set-up-and-manage-the-new-unified-claude-experience-for-your-enterprise-organization))
Limitations to check before switching
- Some enterprise configurations are not supported: organizations using zero data retention, a HIPAA-ready configuration, or customer-managed encryption keys cannot currently enable the unified experience. Anthropic says HIPAA support is expected after general availability and CMEK support is planned for a later release. Organizations that require these configurations should confirm eligibility before planning a transition. ([support.claude.com](https://support.claude.com/en/articles/17444462-set-up-and-manage-the-new-unified-claude-experience-for-your-enterprise-organization))
- General availability does not necessarily mean automatic activation: an admin may need to turn on the capability and confirm its prerequisites. The rollout setting and eligibility can vary by organization configuration. ([support.claude.com](https://support.claude.com/en/articles/17444462-set-up-and-manage-the-new-unified-claude-experience-for-your-enterprise-organization))
- Usage still needs oversight: usage-based pricing remains in place, and agentic work may consume more than a quick answer. Set appropriate limits and watch the unified usage category in reports.
- Outputs need review: Claude returns completed work for inspection. A unified workflow reduces mode switching; it does not remove the need to validate important documents, calculations, code, and decisions.
- Not every control is one switch: access, network egress, connectors, approvals, sharing, and local computer access have distinct settings. Review each relevant policy rather than assuming that enabling or disabling the main capability covers them all. ([support.claude.com](https://support.claude.com/en/articles/17444462-set-up-and-manage-the-new-unified-claude-experience-for-your-enterprise-organization))
Practical tips for employees
To get useful results from Claude Cowork Enterprise, describe the outcome rather than just the first action. Include the intended format, the files or connected sources Claude should use, and any constraints that matter. For instance, specify whether you want a concise summary, a comparison table, or a draft document, and ask Claude to flag missing information instead of filling gaps with assumptions.
For a multi-step assignment, give Claude enough context to distinguish source material from instructions. Check that the right files or connectors are available, and review the output before sharing or using it in a decision. When the task involves sensitive information or an action that could affect external systems, follow your organization’s approval and data-handling rules. If a task needs local folders or desktop apps, confirm that local access is enabled and permitted; the cloud workflow and local computer access are not interchangeable.
Frequently asked questions
Is Claude Cowork Enterprise generally available?
Yes. Anthropic says the unified Claude experience is generally available for Claude Enterprise plans. Organization settings and eligibility requirements still determine whether a particular organization can enable it. ([claude.com](https://claude.com/es/resources/articles/unified-claude-enterprise))
Where can employees use the unified experience?
It is available on web, desktop, and mobile for Enterprise organizations where the Chat and Cowork unified capability is enabled. Members can start a task on one supported surface and continue on another. ([claude.com](https://claude.com/es/resources/articles/unified-claude-enterprise))
Do employees still choose Chat or Cowork?
Not in the unified experience. A conversation begins as chat, and Claude can continue it in a Cowork cloud session when the task calls for agentic work such as running code or working with files. Organizations that have not enabled the unified capability may continue to see separate options. ([support.claude.com](https://support.claude.com/en/articles/17444462-set-up-and-manage-the-new-unified-claude-experience-for-your-enterprise-organization))
Does Efficient mode limit Claude for the whole company?
It can be enabled for the organization or selected custom roles. When it is on, it limits model choices in the unified experience to Sonnet and Haiku; it does not affect other products. New sessions start on Claude Sonnet 5.5 at low effort according to the current admin documentation. ([support.claude.com](https://support.claude.com/en/articles/17444462-set-up-and-manage-the-new-unified-claude-experience-for-your-enterprise-organization))
Can organizations using ZDR, HIPAA-ready settings, or CMEK use it?
No, not currently, according to Anthropic’s setup documentation. Those organizations continue using their current Chat and Cowork configuration until the unified experience supports their required setup. ([support.claude.com](https://support.claude.com/en/articles/17444462-set-up-and-manage-the-new-unified-claude-experience-for-your-enterprise-organization))
Bottom line
Claude Cowork Enterprise brings everyday chat and more involved cloud-based work into one conversation, reducing the need for employees to select a mode up front. The opportunity is a smoother handoff from asking Claude a question to delegating a task and reviewing the result. A thoughtful rollout still depends on role design, connector and network policies, approval settings, cost controls, and a clear understanding of current compliance limitations. For organizations whose configuration is eligible, a limited pilot followed by measured expansion is a practical way to evaluate the unified experience.
