A checklist for rolling out Claude Code to your team

Plan choice, shared config, permission policy and training — grounded in verified facts.

1) Choose a plan

Per claude.com/pricing: Team has a standard seat ($20/mo annual, $25/mo monthly) and a premium seat ($100/mo annual, $125/mo monthly), both including Claude Code and Claude Cowork. Team is the practical default for unified billing/permissions.

2) Decide the shared .claude/

Commit project-level `.claude/` to your repo. Agree upfront on standard subagents/skills, CLAUDE.md's required blocks, and naming conventions.

3) Set a permissions policy

Encode org-wide always-deny rules (e.g. production SSH, `rm -rf`) in the project's `permissions.deny`; leave personal auto-approvals to individual user settings.

4) Stricter control: managed settings

An OS-level managed-settings path (e.g. macOS `/Library/Application Support/ClaudeCode/managed-settings.json`) overrides user settings. Verified absent on this individual, non-managed Mac — it's an enterprise-only layer.

5) Train to avoid uneven results

ConfigDeck's /school offers an 8-module course and per-seat corporate training plans to standardize how the team uses Claude Code.

6) Start small, then expand

Pilot with one team, then roll the working config out as a shared template or ConfigDeck pack for the next team.

FAQ

At what team size should we consider Team plan?

No fixed number — once you want unified billing/permissions, it's worth considering.

Who sets permission rules?

Org-wide always-deny rules go in the shared project permissions.deny; personal preferences stay in individual user settings.

Does this Mac have managed settings?

Verified: no. It's an enterprise-only layer, not needed for individual/non-managed use.

Where can the team train?

ConfigDeck's /school offers an 8-module course and corporate training plans.

See corporate training plans →See ConfigDeck pricing →Find shared packs →