Charlie HillsFree guide · Claude & Claude Code
Claude for Teams: The Full Setup
Run your whole team on Claude two ways: through your org (Chat + Cowork admin toggles) and through one GitHub repo (Claude Code). Exact click-paths, the four roles, and the build to push to invite to pull loop. Team plan, no Enterprise.
Charlie Hills Added 16 June 2026 · Free
What’s inside
- 1How the two layers work
- 2🏢 Part 1: Your org (Claude Chat and Cowork)
- 3💻 Part 2: One GitHub repo (Claude Code)
- 4⚠️ Common mistakes
- 5✅ Start here this week
Your team does not share Claude in one place. It shares two ways: through your org (Chat and Cowork) and through one GitHub repo (Claude Code). The org is a setting you flip. The repo is a file you commit. Set up both and the whole team works from the same brain. No Enterprise plan needed.
How the two layers work
Think of it as two switches.
The org layer is everything you toggle in Claude's settings: who is on the team, what they can spend, which tools they reach, which projects they share. You set it once in the admin console and it applies to everyone instantly. Nothing to install.
The repo layer is for Claude Code. Code does not read your org settings. It reads a folder. So you put your shared rules, skills and agents in one GitHub repo, and every teammate pulls that folder. Change the folder, push it, and everyone has the update next session.
You need both. The org handles people and access. The repo handles the actual work Claude does.
That’s the first part. The rest of this guide is free too.
