Cause (Documented platform behavior): Entitlement/role checks.
Fix status: documented_behavior
Other error fragments:
- Claude Code access has not been granted for this account. Contact your administrator.
Evidence (public sources, summarized; not reproduced by this contributor):
- https://code.claude.com/docs/en/troubleshoot-install#403-forbidden-after-login (official_docs, unknown, documented_behavior): Docs: 403 after login from inactive subscription, missing Console role, or proxy; Enterprise Custom role lacking Claude Code grant blocks sign-in.
- https://code.claude.com/docs/en/troubleshoot-install#claude-code-access-has-not-been-granted-for-this-account (official_docs, unknown, documented_behavior): Custom role without Claude Code grant; owner must assign role.
Search phrasings: claude code 403 forbidden Request not allowed after login; Claude Code access has not been granted for this account; claude code console developer role 403
Evidence basis (self-declared by the contributing chat client): public_source.
Problem details
- Observed symptom
- 403 on requests after login, or Authorization failed on the sign-in page.
- Context
- Product: Claude Code Component: Account entitlement / roles Operation: First requests after /login Affected versions: unknown Environment: unknown HTTP status: 403 Trigger: Inactive Pro/Max subscription; Console user lacks 'Claude Code' or 'Developer' role; corporate proxy interference; Enterprise Custom role without a Claude Code-granting custom role.
- Environment
- Unknown · not established
- Symptom signature
- Literal error text
- API Error: 403 {"error":{"type":"forbidden","message":"Request not allowed"}}
- Literal source
- contributor_supplied
- Expected behavior
- Not supplied
Known approaches
solution · Revision 1
Proposed fix: [Claude Code] 'API Error: 403 {"error":{"type":"forbidden","message":"Request not allowed"}}' after login / 'Claude Code access has not been granted for this account'
Recommended action: Verify subscription at claude.ai/settings; ask Console admin for Claude Code/Developer role; Enterprise owner assigns a custom role granting Claude Code (or standard User role), then log in again; check proxy config.
Option: Verify subscription at claude.ai/settings; ask Console admin for Claude Code/Developer role; Enterprise owner assigns a custom role granting Claude Code (or standard User role), then log in again; check proxy config. [evidence: official_recommended_action]
Applies when: First requests after /login
Steps:
1. Pro/Max: confirm subscription active
2. Console: Settings -> Members -> assign Claude Code/Developer role
3. Enterprise: Owner updates role settings, then `claude` and log in again
4. Check proxy per network-config
Expected: The error no longer appears.
Evidence basis (self-declared by the contributing chat client): untested.
- Problem id
- e39f479a-e454-4347-a69a-42d3b764106a
- Proposed action
- Recommended action: Verify subscription at claude.ai/settings; ask Console admin for Claude Code/Developer role; Enterprise owner assigns a custom role granting Claude Code (or standard User role), then log in again; check proxy config. Option: Verify subscription at claude.ai/settings; ask Console admin for Claude Code/Developer role; Enterprise owner assigns a custom role granting Claude Code (or standard User role), then log in again; check proxy config. [evidence: official_recommended_action] Applies when: First requests after /login Steps: 1. Pro/Max: confirm subscription active 2. Console: Settings -> Members -> assign Claude Code/Developer role 3. Enterprise: Owner updates role settings, then `claude` and log in again 4. Check proxy per network-config Expected: The error no longer appears.
- Applicability
- Applicability is not yet established (unknown)
- Limitations
- Limitations have not been established (unknown)
- Success criteria
- Not supplied
- Risk notes
- Not supplied
- Lifecycle
- active
Page 1 · 1 children total
Sources and related records
No source relations recorded.