Claude Code "OAuth authentication is currently not allowed for this organization": Causes and Fixes

Wokey Team · 2026-10-29

Short answer: OAuth authentication is currently not allowed for this organization means Anthropic's servers refused to let your Claude account's organization use Claude Code through a subscription login. It's a server-side setting on the account, not a problem on your machine. Reinstalling, updating, /logout and /login with the same account all return the same error. For a personal Pro or Max account, check billing first. For a Team or Enterprise account, ask your admin. To keep working in the meantime, authenticate with an API key instead.

What the error looks like

The same server response shows up with different wording depending on the client and the account type:

The raw response is a 403 permission_error today:

{"type":"error","error":{"type":"permission_error","message":"OAuth authentication is currently not allowed for this organization."},"request_id":"req_011C..."}

Claude Code versions from 2025 showed it as API Error: 401 with "type":"authentication_error" and the same message.

Up to at least Claude Code 2.1.295, Pro and Max accounts also got the "Your organization has disabled…" wording, so a personal account seeing it doesn't mean an admin turned something off.

Why reinstalling doesn't help

Anthropic's Claude Code error reference describes this as a server-side organization setting that "can't be overridden from local settings, environment variables, or CLI flags", and running /login again with the same account returns the same error. Public bug reports confirm it: people who logged out and in five times, updated, restarted, cleared ANTHROPIC_API_KEY and tried a second laptop still got it.

The one local check worth doing is that Claude Code is signed in to the account you think it is. Run /status in Claude Code, or claude auth status in a shell, and look at the login method, organization and email.

Causes by account type

Personal Pro or Max

1. A payment problem. This is the most common cause, and recent Claude Code versions say so in the error itself. Look for a failed renewal, an expired card, or a second subscription you forgot about. In one public report, a Max plan bought through the Android app was active, but a duplicate Max subscription billed directly by card was unpaid, and Claude Code broke two days after the app renewal. In another, the reporter closed the issue with "I didn't pay." Open claude.ai/settings/billing, settle anything overdue, and try again a few minutes later.
2. The subscription is attached to a different organization. One email address can own several organizations: a personal one, a Console (API) one, a team you joined. If Claude Code resolves to an organization without the subscription, it gets this error even though chat on claude.ai works. Anthropic support has described this as an entitlement mapping issue that "can't be fixed from your end". Contact support, include the organization shown by /status, and ask them to check which organization Claude Code resolves to.

Team or Enterprise

1. Claude Code isn't enabled for your organization, role or group. On Enterprise, admins can scope features to custom roles and groups, so your developer group may not include Claude Code.
2. Your seat doesn't include Claude Code. Every Team seat includes it, as does every seat on new and self-serve Enterprise plans. On older Enterprise plans, only "Chat + Claude Code" and Premium seats do; Standard and Chat-only seats don't.
3. You no longer have a seat. Removed members, and users whose directory sync (SCIM) left them "Unassigned" because no seat was free, lose access.

Admins change seat types under Organization settings > Members and buy or reassign seats under Organization settings > Organization. If you're the admin and see no option to enable access, contact Anthropic support.

Third-party tools that sign in with a Claude account

Tools and plugins that reuse your Claude login show the raw message. The cause is the same account-level state, so check billing and the organization first. Anthropic's documentation says subscription sign-in is meant for Claude Code and Anthropic's own apps, and that developers building on the Agent SDK should authenticate with an API key.

Don't confuse it with these

Keep working with an API key

This is what Claude Code itself suggests. An API key is billed per token instead of through your subscription, and it works regardless of the organization's subscription setting. There are two ways to use one.

An Anthropic Console key. Create a key at platform.claude.com and export it before starting claude. In interactive mode, Claude Code asks once whether to use it:

export ANTHROPIC_API_KEY="sk-ant-..."

An Anthropic-compatible gateway, such as Wokey. Wokey uses the same Claude model IDs and bills per token. Put the gateway address and your Wokey key in ~/.claude/settings.json:

{
  "env": {
    "ANTHROPIC_BASE_URL": "https://api.wokey.ai",
    "ANTHROPIC_AUTH_TOKEN": "your Wokey API key"
  }
}

ANTHROPIC_AUTH_TOKEN takes precedence over the subscription login, so you don't need to log out first. Restart Claude Code and run /status: the Anthropic base URL line should read https://api.wokey.ai. Leave out /v1; see the base URL guide for the details. Keys are created on the API keys page.

Things to know before you switch:

• Features tied to your claude.ai login stop working, such as claude.ai connectors, /schedule and Remote Control.
• The Claude desktop app ignores these variables. Its Code tab needs the gateway configured under Developer → Configure Third-Party Inference; see using the desktop app with a third-party API.
• Company-managed machines may refuse API keys. If your admin deployed managed settings such as forceLoginMethod, forceLoginOrgUUID or allowedProviders, Claude Code rejects ANTHROPIC_API_KEY and ANTHROPIC_AUTH_TOKEN at startup or blocks custom endpoints. That is company policy rather than a bug: talk to your admin, and check your company's rules before using a personal key on company code.

When your subscription access comes back, remove the two variables from settings.json and Claude Code goes back to your claude.ai login.