Claude Code for teams and enterprises

Rolling Claude Code out to a team means six decisions, in order: how traffic leaves the network, which provider serves the model, which configuration lives in the repository, which policy managed settings enforce, where sessions run, and who can start work from Slack. Each has its own page below and leaves evidence that it holds.

This hub is for the tech lead moving Claude Code from pilot to team, and the developer setting it up when the proxy blocks sign-in or security wants the MCP allowlist first. Checked against Claude Code v2.1.283 (latest channel) on 2026-09-26.

Which Claude Code team page answers your question?

Your question	Page
Sign-in fails behind the proxy, VPN or TLS inspection	Proxy and VPN configuration
Traffic must go through Bedrock, Google Cloud, Foundry or our own gateway	LLM gateway configuration
How do we share `CLAUDE.md`, settings, MCP servers, skills and hooks through the repository?	Team collaboration with shared Claude Code config
How do we give everyone one environment with locked-down egress?	Dev container setup for Claude Code
How do we enforce permissions, models and MCP allowlists developers cannot override?	Enterprise integration and security
How do we let anyone tag `@Claude` in Slack under a shared team identity?	Claude Tag: a shared Claude Code identity in Slack

Running Codex or Cursor too? Use one managed policy across every coding agent. Deciding where the model may run at all? Start with where the model runs.

In what order should you roll Claude Code out to a team?

A managed policy is useless if half the team cannot authenticate, so order matters.

Get traffic out. Configure the proxy and custom CA, then confirm on a clean machine that claude doctor passes and a session reaches the model.
Pick the model route. Use a Team or Enterprise plan, or route through Bedrock, Google Cloud’s Agent Platform (formerly Vertex AI), Foundry or a gateway. Features differ: Ultrareview is not offered on Bedrock, Google Cloud or Foundry, and auto mode supports fewer models there (Anthropic docs, checked 2026-09-26). Versions: models hub.
Commit the shared project config. CLAUDE.md (or AGENTS.md), .claude/settings.json with the team’s allow and deny rules, .mcp.json, skills and hooks, all under CODEOWNERS.
Enforce the floor with managed settings. Managed settings rank above command-line arguments and every local, project and user file, so developers cannot override them. Deliver them as managed-settings.json, through MDM, or from the claude.ai admin console (Team and Enterprise). Pin the channel here too: autoUpdatesChannel: "stable" runs about a week behind latest.
Standardise where sessions run. A dev container gives every developer and CI job the same version, tools and egress firewall. Run unattended sessions only in a disposable, network-restricted container.
Open delegation last. Pilot Claude Tag in one Slack channel once review gates exist, and require that its changes reach the default branch only through pull requests that pass the same CI and CODEOWNERS review as human work.

Audit this repository's shared Claude Code configuration for a team rollout. Do not edit
any files. Read CLAUDE.md or AGENTS.md, .claude/settings.json, .mcp.json, .claude/skills/,
.claude/agents/, any hooks in the settings, .devcontainer/ and CODEOWNERS. Report:
1. Every permission allow rule that lets Claude run a command which can push, deploy,
   delete data or read secrets, with the file and line.
2. Every MCP server, with its transport, what it can reach, and whether it needs a
   credential that is not in an environment variable.
3. Settings that only work on one person's machine: absolute paths, personal tokens,
   tools that are not installed in the dev container.
4. Settings a project file cannot set: defaultMode "auto" or "bypassPermissions" is
   ignored in project settings and belongs in user or managed settings.
5. Which of these files CODEOWNERS does not protect.
End with a table: finding, risk (high, medium, low), and the one-line fix.

Draft a managed-settings.json proposal for our Claude Code rollout. Do not write it to
any system path; print it and explain it. Start from .claude/settings.json in this
repository and propose only:
1. permissions.deny rules for commands no developer should run through Claude here
   (deploys, production database writes, reading .env or credential files).
2. permissions.disableBypassPermissionsMode set to "disable".
3. autoUpdatesChannel set to "stable", so every seat runs the same release.
4. availableModels limited to the models we name: <list the models you approved>.
For each entry, give one command I can run on a developer machine that proves the rule
is in force (for example, a denied command that must still be refused after the
developer allows it in .claude/settings.local.json). Flag any key you are not sure
exists instead of guessing.

New teammates then follow one routine: onboard a new teammate onto the shared setup.

How do you prove the team setup holds without watching every session?

Each layer produces evidence, and someone owns it.

Evidence	What it proves	Owner
The onboarding smoke test passes on a freshly imaged laptop	Network, auth and shared config work outside the pilot	Tech lead
A managed-denied command stays refused after a developer allows it locally	Managed settings are in force and win over local files	Platform or security owner
The dev container’s CI job passes a known `claude -p` task	The shared environment builds and reaches the model	Tech lead
Analytics dashboard (Team and Enterprise) for active users and merged pull requests; OpenTelemetry (`CLAUDE_CODE_ENABLE_TELEMETRY=1` plus an `OTEL_METRICS_EXPORTER`) for per-developer cost, which the dashboard lacks	Adoption is real and spend is inside budget	Engineering manager

For budgeting, Anthropic cites “around $13 per developer per active day and $150-250 per developer per month” for enterprise deployments (Anthropic costs documentation, checked 2026-09-26). See pricing analysis, cost control, and the evidence bundle each agent pull request must carry.

What breaks when Claude Code goes from one developer to a team?

Symptom	Cause	Recovery
Two developers get different default models	Mixed channels: on 2026-09-26 `stable` (2.1.274) gives Team Standard seats Sonnet 5, `latest` (2.1.283) gives Opus 5.5	Set one `autoUpdatesChannel` in managed settings and restrict the choice with `availableModels`
The team’s `defaultMode` in `.claude/settings.json` has no effect	`auto` and `bypassPermissions` are ignored in project settings	Set it in managed or user settings; turn auto mode off org-wide with `permissions.disableAutoMode: "disable"` in managed settings
Usage still bills personal subscriptions after a gateway rollout	Only `ANTHROPIC_BASE_URL` was set; the claude.ai login stays active	Also give Claude Code a gateway credential (`ANTHROPIC_AUTH_TOKEN`, `ANTHROPIC_API_KEY` or `apiKeyHelper`), as in LLM gateway configuration