Once Claude Code reaches your company, someone has to answer who signs in with which account, who pays, and how to keep personal and work use apart. This official page walks through every way in: personal account, team plan, Console or your own cloud. It also covers how an admin can require that every login belongs to the organization.
Who this is NOT for
If you don't use Claude Code yet, this page is not for you: it is the front door to a terminal tool, not a product of its own. Start with the Claude Code card. If you work alone with a single account, you don't need to read all of it either: type `claude`, sign in through the browser and you're done. The rest is for whoever runs a team.
The value isn't the login step, which is trivial. It's what the page settles for a team: it recommends Claude for Teams or Enterprise for most teams because of centralized billing and management, and admins can require every claude.ai account to belong to the organization. Two details cost people time. If the machine has an ANTHROPIC_API_KEY variable, Claude Code asks whether to use it, and if you say yes it skips the login: choose deliberately which credential you work with. If you split work and personal accounts with CLAUDE_CONFIG_DIR, the page itself warns that two Console sign-ins without an API key are not kept apart. It lists no license or repo metrics because it is documentation, not a code project.
Your first step
Open your terminal, type claude and finish signing in through the browser. If the browser doesn't open on its own, press c to copy the link. If you get a code instead of being sent back to the terminal (common in WSL2, SSH and containers), paste it at the "Paste code here" prompt.
The Claude Code — Authentication (documentación oficial) implementation guide
The project belongs to code.claude.com and it is free: the link beside asks for nothing. The guide to set it up without getting lost is ours: step by step, common mistakes and a checklist. Leave your email and we will send it.
No spam. Unsubscribe anytime.