Solution skill
Roles missing in the access token - RBAC settings and permissions flag
Complete solution
Symptom: the user has roles in the dashboard but the token has no roles or permissions. Cause: the API's RBAC toggles are off, or roles live at the org level. Confirmation: compare the token claims with the user's dashboard roles. Not for different error messages.
TL;DR: Symptom: the user has roles in the dashboard but the token has no roles or permissions. Cause: the API's RBAC toggles are off, or roles live at the org level. Enable RBAC alone changes the authorization model; the second toggle is what puts permissions in the token. Confirm - Decode the access token (not the id token).
The fix
- API RBAC settings off: Applications > APIs > your API > Settings > "Enable RBAC" and "Add Permissions in the Access Token" are both required. Enable RBAC alone changes the authorization model; the second toggle is what puts
permissionsin the token. - Permissions assigned to the role but the role not assigned to the USER (assigned to nobody, or to another user).
- Organization roles: org-level roles appear in the token only when the login included the organization context. A login without
organizationgets no org roles. - Looking at the id token - permissions go in the ACCESS token, not the id token.
- Caching: the token was minted before the role assignment. Tokens are snapshots.
- Decode the access token (not the id token). Check
permissionsarray andscope. - Management API: fetch the user's roles from the users endpoint to see ground truth.
- Tenant logs: the login event's details sometimes include the evaluated permissions.
When to use this
- You are seeing this exact error message; match the block above, not just part of it.
- The failing call matches the scenario in the title: Roles missing in the access token - RBAC settings and permissions flag.
- You want the fastest verified fix before digging through logs.
When not to use this
- Your error text differs from the block above; close cousins often have different causes.
- The stack trace points at a different component than the one in the title.
- You already applied this fix and the error persists; look for a second cause instead of reapplying.
Compatibility
- Not pinned to a specific version; follows current Roles behavior.
Evidence
Auth0's RBAC docs describe role-based access control, assigning permissions to roles and roles to users, and the API settings for RBAC. The 'Add Permissions in the Access Token' setting is documented in the API authorization settings. Verified against live docs 2026-09-26.
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_iBXNpTO6yZxALebGSh3Vlw" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Roles missing in the access token - RBAC settings and permissions flag <span>— Vectle</span></a>