Purpose
In September 2026 chat and Cowork became one Claude for Pro and Max. On October 23, 2026 the unified
experience became generally available for Claude Enterprise. Conversations start as chats; when a task
needs code or file work, Claude continues in the cloud and returns a finished document, analysis, or deck.
This skill turns the announcement into an admin rollout procedure. Facts come from the post; anything
organization-specific is yours to decide.
When to use
- You administer a Claude Enterprise organization and are about to enable the unified experience.
- Security asks how cloud sessions, connectors, and data are protected.
- Finance asks how agentic (cloud) work affects usage-based spend and how to cap it.
- You need to explain to end users what changes and what carries over.
Instructions
- Check eligibility first. Organizations using zero data retention for Claude Code, a HIPAA-ready
configuration, or customer-managed encryption keys stay on their current configuration. Confirm which
applies to you before planning.
- Explain what changes for users.
- One Claude across web, desktop, and mobile.
- Simple questions get quick chat answers; code or file tasks continue in the cloud and come back as
finished outputs.
- Cloud work keeps running after a laptop is closed and can be resumed on any platform.
- Chats, projects, connectors, skills, and plugins carry over.
- Review the security posture with your security team using
references/security-posture.md (SSO and Compliance API, encryption,
no training by default, one isolated VM per cloud session, network egress off by default, connector
credentials outside the sandbox, central visibility). Point them to the security best practices guide
on the Anthropic Trust Center.
- Set cost controls before broad enablement. Pricing stays usage-based, and agentic work can use more
tokens than quick chats. Choose a setting for each of the four admin controls in
references/cost-controls.md:
efficient mode, model entitlements per role, spend limits (organization / group / member), and pooled
group budgets.
- Fill in the rollout plan with templates/rollout-checklist.md:
pilot groups, entitlements, limits, comms, and review dates.
- Enable it in Organization settings, where admins manage the rollout. Follow the admin setup guide
linked from the post (support.claude.com, article 17444462). Existing Enterprise customers also receive a
rollout email.
- Review spend and usage after launch and adjust entitlements, limits, or efficient mode by group.
Examples
Example 1 - cost-conscious first wave
- Pilot: one analytics group with a pooled monthly group budget.
- Everyone else: efficient mode on (Sonnet and Haiku), member spend limits set.
- Model entitlements: Opus 5.5 only for roles that need heavy analysis.
- After a month, widen entitlements where the pilot showed value.
Example 2 - security briefing answer
"Each cloud session runs in its own isolated virtual machine, network egress is off by default on
Enterprise, connector credentials are stored outside the sandbox, data is encrypted in transit and at
rest and not used for training by default, and our SSO and Compliance API controls still apply."
Example 3 - not eligible yet
An organization with customer-managed encryption keys keeps its current configuration; the admin records
this in the checklist and does not plan an enablement date.
Notes
- Model efficiency figures quoted in the post: Opus 5.5 costs 40% less than Opus 5 on typical workloads;
Sonnet 5.5 costs up to 30% less than Sonnet 5 for most work.
- The post includes customer stories (DXC, LifeMoves, Quantium, Carvana); see the original for details.
- Source: https://claude.com/resources/articles/unified-claude-enterprise
1---2name: enterprise-unified-rollout3description: Plan and run an organization-wide rollout of the unified chat + Cowork experience on Claude Enterprise (generally available October 23, 2026) - confirm eligibility, review the security posture, and set cost controls (efficient mode, model entitlements, spend limits, pooled group budgets) before enabling it in Organization settings. Use when an Enterprise admin, IT, security, or finance owner must decide how and for whom to turn on the unified experience, or must explain how cloud task work is secured and paid for.4metadata:5 source: https://skillmd.com/skills/uygnoey/enterprise-unified-rollout6---78## Purpose9In September 2026 chat and Cowork became one Claude for Pro and Max. On October 23, 2026 the unified10experience became generally available for Claude Enterprise. Conversations start as chats; when a task11needs code or file work, Claude continues in the cloud and returns a finished document, analysis, or deck.12This skill turns the announcement into an admin rollout procedure. Facts come from the post; anything13organization-specific is yours to decide.1415## When to use16- You administer a Claude Enterprise organization and are about to enable the unified experience.17- Security asks how cloud sessions, connectors, and data are protected.18- Finance asks how agentic (cloud) work affects usage-based spend and how to cap it.19- You need to explain to end users what changes and what carries over.2021## Instructions221. **Check eligibility first.** Organizations using zero data retention for Claude Code, a HIPAA-ready23 configuration, or customer-managed encryption keys stay on their current configuration. Confirm which24 applies to you before planning.252. **Explain what changes for users.**26 - One Claude across web, desktop, and mobile.27 - Simple questions get quick chat answers; code or file tasks continue in the cloud and come back as28 finished outputs.29 - Cloud work keeps running after a laptop is closed and can be resumed on any platform.30 - Chats, projects, connectors, skills, and plugins carry over.313. **Review the security posture** with your security team using32 [references/security-posture.md](references/security-posture.md) (SSO and Compliance API, encryption,33 no training by default, one isolated VM per cloud session, network egress off by default, connector34 credentials outside the sandbox, central visibility). Point them to the security best practices guide35 on the Anthropic Trust Center.364. **Set cost controls before broad enablement.** Pricing stays usage-based, and agentic work can use more37 tokens than quick chats. Choose a setting for each of the four admin controls in38 [references/cost-controls.md](references/cost-controls.md):39 efficient mode, model entitlements per role, spend limits (organization / group / member), and pooled40 group budgets.415. **Fill in the rollout plan** with [templates/rollout-checklist.md](templates/rollout-checklist.md):42 pilot groups, entitlements, limits, comms, and review dates.436. **Enable it in Organization settings**, where admins manage the rollout. Follow the admin setup guide44 linked from the post (support.claude.com, article 17444462). Existing Enterprise customers also receive a45 rollout email.467. **Review spend and usage after launch** and adjust entitlements, limits, or efficient mode by group.4748## Examples49**Example 1 - cost-conscious first wave**50- Pilot: one analytics group with a pooled monthly group budget.51- Everyone else: efficient mode on (Sonnet and Haiku), member spend limits set.52- Model entitlements: Opus 5.5 only for roles that need heavy analysis.53- After a month, widen entitlements where the pilot showed value.5455**Example 2 - security briefing answer**56"Each cloud session runs in its own isolated virtual machine, network egress is off by default on57Enterprise, connector credentials are stored outside the sandbox, data is encrypted in transit and at58rest and not used for training by default, and our SSO and Compliance API controls still apply."5960**Example 3 - not eligible yet**61An organization with customer-managed encryption keys keeps its current configuration; the admin records62this in the checklist and does not plan an enablement date.6364## Notes65- Model efficiency figures quoted in the post: Opus 5.5 costs 40% less than Opus 5 on typical workloads;66 Sonnet 5.5 costs up to 30% less than Sonnet 5 for most work.67- The post includes customer stories (DXC, LifeMoves, Quantium, Carvana); see the original for details.68- Source: https://claude.com/resources/articles/unified-claude-enterprise