From the Anthropic edition of November 5, 2026
Claude for Government Nov. 4–5 notes: full seat tiers block SCIM adds, and Cowork defaults keep changing on Desktop
Anthropic · U.S. government AI productivity (federal/state/local eligible product) · United States (Claude for Government tenants)
- Publisher
- Claude for Government documentation
- Original publication
- November 5, 2026 (release 2026.11.05.1; also 2026.11.04.1)
- Source retrieved
- 2026-11-06
- Event date
- 2026-11-05
What happened
Anthropic's Claude for Government changelog for 2026.11.05.1 states that group mappings apply at first sign-in for directory-synced members, and if the mapped or 'New members start here' seat tier is full, the signing-in member gets no seat and SCIM does not add or re-enable them. Related Nov. 3–5 notes warn that turning off Chat or Advanced file analysis may have no effect for members who have Cowork on newer Desktop builds after November 10, document AppArmor/sandbox breakage on some Linux hosts, and change analytics so only answered requests count as active use. These are operational product changes, not measured mission outcomes.
Why it matters
Cross-tag state-government: state and local tenants on Claude for Government must adjust SCIM seat-capacity planning and Desktop configuration baselines before directory waves, or new staff can authenticate yet receive no seat. The notes are concrete operating constraints for public-sector admins.
Evidence and measured results
Primary vendor changelog entries dated 2026.11.05.1, 2026.11.04.1, and nearby Nov. 3 Desktop notes. No third-party audit of the seating behavior is cited.
Limitations and uncertainty
Vendor changelog only; living page. Does not report how many tenants are affected or mission impacts. Some breaking Desktop behaviors depend on version cutovers later in November.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-11-06; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Agencies expanding Claude for Government via SCIM risk new staff signing in without seats when tiers are full, plus Desktop setting drift around Cowork.
- Stakeholders
- Tenant admin
- Identity / IAM
- Endpoint management
- Agency CIO
- Help desk
- Discovery questions
- What buffer exists above mapped group size for each seat tier?
- Which Desktop build is mandated before Nov. 10?
- Do Linux Code users have an AppArmor bubblewrap profile?
- Value hypothesis
- Interpretation: a short readiness engagement can prevent onboarding outages and unintended Cowork enablement when directory waves hit.
- Potential engagement
- A one-to-two-week Claude for Government admin readiness review covering SCIM seating and Desktop baselines.
- Unsupported claims
- That SCIM failures are fixed
- Mission productivity gains from these releases
- That Chat-off policies remain effective wherever Cowork is on
Pre-sales engineering
Role takeaway
- Fit
- Directly applicable to Claude for Government tenants using directory sync and Claude Desktop.
- Architecture and integration
- IdP SCIM → seat tier mappings → Desktop managed settings; monitor gateway minimum Claude Code versions.
- Prerequisites
- Seat-capacity monitoring
- Staging IdP group
- Managed Desktop channel
- Linux sandbox profile where Code is allowed
- Constraints
- Full tiers block adds
- Version-gated Desktop behavior
- Possible unsandboxed Code on AppArmor-blocked hosts
- Security
- Verify sandbox enforcement on Linux; treat unsandboxed Code as a policy exception requiring compensating controls.
- Proof of value
- Staging sync of N users with zero unseated actives
- Desktop config matches intended Chat/Cowork/Code matrix
- Sandbox self-test passes on approved Linux images
Delivery
Role takeaway
- Work
- Update runbooks, add seat alerts, schedule Desktop updates, and brief help desk on 'no seat' sign-in symptoms.
- Dependencies
- Seat purchases or reallocation
- Endpoint packaging
- IdP admin time
- Ownership
- Tenant admin owns seating; endpoint team owns Desktop; IAM owns SCIM mappings.
- Skills and adoption
- Admin workshop on group mapping priority and Desktop home settings.
- Governance checkpoints
- Pre-sync capacity sign-off
- Post-sync exception review
- Pre-Nov-10 Desktop baseline freeze
- Acceptance criteria
- No production sync when mapped tier utilization exceeds agreed threshold
- Help desk script for unseated users
- Documented Linux Code host requirements
- Risks
- Mass unseated onboarding
- Cowork enabled contrary to policy
- Unsandboxed shell exposure
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
Capacity must be provisioned before SCIM enablement of large groups; Desktop home/Cowork settings need a managed configuration profile because UI toggles alone may not stick after Nov. 10 on newer builds.
Governance
Who approves, reviews and stays accountable for outcomes?
Seat-tier mapping and 'New members start here' are now high-impact governance controls—mis-sizing creates silent access failures for onboarded staff.
Security and privacy
What data, permissions and controls need testing?
Linux Code sessions where AppArmor blocks the sandbox may run shell commands unsandboxed on affected Desktop versions—agencies should verify host profiles before allowing Code.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Unseated new hires create immediate workforce friction; changelog also notes screen-reader work in older entries but Nov. 4–5 items are mainly seating/Desktop behavior.
Procurement
What should contracts, pricing and exit terms secure?
Seat buffers and Desktop fleet updates are now operational cost drivers tied to directory growth, not optional polish.
Operating model
Which teams own the service once it runs?
Identity, endpoint, and Claude admins must operate as one control plane; analytics that once counted app opens will understate or redefine adoption.
Publication history
- 2026-11-05Anthropic · Issue 085 resources
Stable resource ID: claude-for-government-changelog-scim-seating-cowork-defaults-20261105