Theme
Access Problems
What you see
A page, action, or scoped record is missing.
What it usually means
The account may be signed out, assigned to a different scope, missing the required community role, outside a subscription, or using a disabled module.
Safe checks and resolution
Sign in again, confirm profile and scope, check the current navigation and availability message, then ask the responsible manager to verify the assignment.
When to contact an authorized manager
Ask for help when the issue depends on role assignment, community scope, review status, or a locked workflow. Include the page name, visible message, selected scope, approximate time, and the safe steps already tried. Do not include passwords, tokens, private keys, or unrelated personal data.
Related guides
Practical depth
Evidence that resolves access issues
Compare account approval, player link, membership, scope, role, plan or grant, quota, and the exact access message. Reopen from current navigation before reporting the page, action, community, and time.
Worked example, recovery, and limitations
What you see: Analytics appears in navigation, but a kingdom view says access is unavailable. Checks: Verify the signed-in account, active kingdom, matching assignment, accepted grant state, effective feature, and any suspension or quota message. Decision: If the grant is pending, acceptance is the recovery; if it is accepted but the user lacks a matching scope, an authorized manager must correct the assignment. Output: Access either resolves for the intended read-only view or the responsible gate is named. A subscription cannot add management permission, and a role cannot bypass a disabled feature. Include the page, scope, role label, grant state, and exact message in support evidence. Never include credentials.
Use the scope switcher, account status, assignment label, feature message, and usage panel as diagnostic controls. A visible denial cannot reveal private permission internals and does not guarantee that another scope will qualify.