The Claude Code logo. Image: Anthropic
“Your organization has disabled Claude subscription access for Claude Code” means the Claude organisation your login belongs to doesn’t let Claude Code sign in with a subscription, according to Anthropic’s Claude Code error reference. On a Team or Enterprise plan the fix is your admin. On a personal Pro or Max plan, where there’s no admin to ask, it’s usually Claude Code picking the wrong organisation for your account, and there are a few things to try before you contact support.
The full message reads:
Your organization has disabled Claude subscription access for Claude Code
· Use an Anthropic API key instead, or ask your admin to enable access
Last checked: September 30, 2026.
Jump to:
What it means
Similar errors
Work and personal accounts
FAQ
What does “your organization has disabled Claude subscription access” mean? #
Every Claude account sits inside an organisation. On a Team or Enterprise plan that’s your company; on a personal plan it’s a personal organisation tied to your account. When you sign in to Claude Code with /login, it checks whether that organisation allows subscription logins for Claude Code. If the answer is no, you get this error.
Anthropic says this is “a server-side organization setting, so it can’t be overridden from local settings, environment variables, or CLI flags.” Running /login again with the same account returns the same error. If you use Claude Code through the Agent SDK or in non-interactive mode (claude -p), the same problem shows up as the error code oauth_org_not_allowed.
Why does it say “your organization has disabled Claude” on a personal Pro or Max plan? #
This is the case that confuses most people, and the one the bug reports on Anthropic’s own Claude Code GitHub are full of: individual Pro and Max subscribers with no team, no admin and no API key set, blocked by a message telling them to ask their admin.
In one of those reports, Anthropic support told a Pro subscriber it was “a server-side entitlement mapping issue that can’t be fixed from your end.” In that case, the same email address had three organisations, two of them with exactly the same name (one on the Free plan, one on Pro), and Claude Code was resolving to the wrong one. Support said a human agent would need to check “which organization ID Claude Code is resolving to” and either enable access for it or link the subscription to the right organisation.
Here’s what to try, in order:
- Run
/status. It shows your login method, organisation and email. If the organisation is blank, or isn’t the one you pay for, that’s your problem. - Check for a stray API key. Run
echo $ANTHROPIC_API_KEY(orecho %ANTHROPIC_API_KEY%on Windows). If it prints anything, unset it and remove it from your shell profile or.envfile. Keys take priority over your subscription login. - Log out and back in. Type
/logout, then runclaude, choose to sign in with your Claude subscription, and on the authorisation page make sure the organisation selected is the one with your Pro or Max plan. - Update Claude Code. At least one report says the error started after an update, so make sure you’re on the latest version.
- Contact Anthropic support. If none of that works, the fix is on Anthropic’s side. Go tosupport.claude.com , say you’re on a personal plan with no organisation admin, and include the feedback ID from
/feedbackif it works for you. Ask them to check which organisation ID Claude Code resolves to.
This is a sign-in problem, not a usage limit, so it isn’t fixed by waiting. If your issue is running out of messages instead, see our guide to Claude’s usage limit resets.
How do I fix it on a Team or Enterprise plan? #
If your account belongs to a company plan, the error usually means exactly what it says. The Claude Code docs tell you to ask your admin to enable Claude Code access for your organisation, and if you are the admin and can’t see an option to do it, to contact Anthropic support.
| Your plan | Is Claude Code included? | What to ask your admin |
|---|---|---|
| Team | Every seat | Check you’ve been invited to the right organisation and have an active seat |
| Enterprise (new and self-serve) | Every seat | Check your seat is assigned and Claude Code hasn’t been turned off for your role |
| Older Enterprise plans | Only “Chat + Claude Code” or Premium seats | Move you to a Chat + Claude Code or Premium seat |
That’s based on Anthropic’s help article on using Claude Code with a Team or Enterprise plan, which says owners manage seat assignments in Organization settings. On Enterprise plans with role-based permissions, anything switched off at organisation level can’t be switched back on by a custom role, so the fix has to come from an owner.
Some companies also lock Claude Code to their own organisation on purpose, using the forceLoginMethod and forceLoginOrgUUID settings described in the Claude Code authentication docs. On a work laptop, that can stop you signing in with a personal account at all.
Can I use an Anthropic API key instead? #
Yes, and it’s the workaround the error message itself suggests. Create a key in the Claude Console, then either set it as ANTHROPIC_API_KEY or sign in with your Console account from the /login screen. Claude Code approves the key once and remembers your choice.
The catch is cost. API usage is billed per token, separately from any Pro, Max or Team plan, so you’d be paying twice while your subscription is stuck. Our guide to what Claude Code costs explains how the two billing routes compare. And remember to remove the key once your subscription works again: Claude Code uses an API key ahead of your subscription login whenever one is set.
Similar Claude Code organisation errors, and what each one means #
A few messages look alike but have different causes. Here’s how to tell them apart, using Anthropic’s error reference:
| Message | What’s happening | Fix |
|---|---|---|
| Your organization has disabled Claude subscription access for Claude Code | Your organisation (or the one Claude Code picked) doesn’t allow subscription logins | Admin, or Anthropic support on a personal plan |
| API Error: 400 This organization has been disabled | An old ANTHROPIC_API_KEY from a disabled Console organisation is overriding your login |
Unset the key, relaunch, check /status |
| Your ANTHROPIC_API_KEY belongs to a disabled organization | Same as above, in newer versions of Claude Code | Unset the key; run /login if you have no saved login |
| Your organization has disabled API key authentication | Your Console admin has turned off API keys | Unset the key or remove apiKeyHelper , then/login |
| Your account is on hold and can’t use Claude Code | The account itself has been suspended | Follow the link to claude.ai/restricted to see details or appeal |
Messages as shown in Anthropic’s Claude Code error reference, September 2026.
None of these are about where you live. If a sign-in error mentions your country instead, see our guide to where Claude is available. And if Claude Code suddenly won’t sign in for everyone at once, check status.claude.com: during Tuesday’s outage, sign-in and Claude Code were among the first things to break.
How do I use Claude Code with a work account and a personal account? #
Mixing a company login and a personal plan on the same machine is an easy way to end up signed in to the wrong organisation. Anthropic’s docs suggest giving each account its own configuration folder with the CLAUDE_CONFIG_DIR environment variable. In Bash or Zsh, for example:
alias claude-work='CLAUDE_CONFIG_DIR=~/.claude-work claude'
Then claude-work uses your work login, and plain claude keeps your personal one. Each folder has its own settings, history and login.
Frequently asked questions #
What does “Your organization has disabled Claude subscription access for Claude Code” mean?
It means the Claude organisation your login belongs to doesn’t allow Claude Code to sign in with a subscription (Pro, Max, Team or Enterprise). Anthropic says it’s a server-side setting, so running /login again, changing local settings, environment variables or CLI flags won’t clear it.
Why do I get this error on a personal Pro or Max plan?
You shouldn’t, since a personal plan has no admin. When it happens, Anthropic support has told users it’s “a server-side entitlement mapping issue”: Claude Code is picking the wrong organisation ID for your account, often when the same email has more than one organisation. Only Anthropic support can fix that mapping.
How do I fix it?
If you’re on a Team or Enterprise plan, ask your admin to give you a seat that includes Claude Code. If you’re on a personal plan, run /status to see which organisation is in use, log out and back in making sure you authorise the organisation that holds your subscription, and if that fails, contact Anthropic support with your feedback ID. A Console API key works as a stopgap, but it’s billed separately.
Can I fix it by using an API key?
Yes, as a workaround. Claude Code will run on a Claude Console API key, but API usage is billed per token on top of any subscription you already pay for. Remove the key again (unset ANTHROPIC_API_KEY) once your subscription login works, or Claude Code will keep using it.
What does “API Error: 400 This organization has been disabled” mean in Claude Code?
It’s a different problem: Claude Code is using an old ANTHROPIC_API_KEY that belongs to a disabled Console organisation, and the key overrides your subscription login. Unset the variable, remove it from your shell profile or .env file, relaunch Claude Code and run /status to confirm your subscription is in use.
What does “Your organization has disabled API key authentication” mean?
It’s the opposite case: your Console organisation’s admin has switched off API keys, so Claude Code’s key is rejected. Unset ANTHROPIC_API_KEY (or remove an apiKeyHelper setting) and run /login to sign in with your Claude account instead.
Does this error mean Claude Code isn’t available in my country?
No. It’s about the organisation your account belongs to, not where you are. If a sign-in error does mention your country, check Anthropic’s supported countries list and turn off any VPN.
How do I use Claude Code with both a work and a personal account?
Give each account its own configuration folder with the CLAUDE_CONFIG_DIR environment variable, for example an alias called claude-work that points to ~/.claude-work. Each folder keeps its own login, so a work organisation’s rules don’t get mixed up with your personal plan.