Claude’s Enterprise updates on November 5 and 6, 2026 bring security management and spending attribution into closer view. Anthropic announced security and administration features on November 5, followed by a beta for tracking project spend with organizational cost codes on November 6.
Together, the changes address two recurring questions in an enterprise rollout. A security owner needs to understand how the service is configured and what access it permits. A budget owner needs to connect usage with the team, client or project receiving the benefit.
Security configuration becomes easier to review
Anthropic’s announcement describes a security center that compares organization settings with its recommended configuration. It also describes generally available inference hooks, which connect supported prompts and tool calls to a company’s data-security tools. Several other administration features remain in beta.
Our operational interpretation is that a centralized view is most useful when a team assigns responsibility for its findings. For each configuration item under review, record the owner, the expected setting and the reason for any accepted exception. That creates a manageable review process as features and requirements change.
Different controls answer different access questions
The update spans centralized management, member sign-out and additional access controls. Deployment teams should check the availability and scope of the particular control they intend to use, rather than treating the announcement as a single switch that covers every Claude environment.
A practical access review can follow one employee through normal onboarding, a role change and departure. Check which managed organization grants access, which connected resources remain available and how the employee’s active work is handled. Record the outcome at each boundary so the organization has a repeatable procedure.
Cost-code tags give projects a business reference
The project-tags beta lets eligible Enterprise organizations attach codes they already use, such as a charge code or client-matter number, and view most project spend by tag. Anthropic documents access through organization settings and the API.
The word “most” matters for financial reconciliation. Our recommendation is to start by comparing tagged reporting with the organization’s overall usage records. Decide which expenses belong in a project report, where unallocated spend should appear and who corrects a project that uses the wrong code.
Use the rollout to establish ownership
A useful first implementation pairs a small project-tag pilot with a documented security review. Choose a few projects with known owners and compare reported spending with the actual work performed. At the same time, test the relevant access and policy controls in the supported product environment.
This creates a shared operating picture for finance, IT and the people using Claude. The result to look for is a project whose owner can explain its access, its spending attribution and the work that spending produced. Expand the rollout when those records can be reconciled consistently.