service_shell Service page (403 Access Denied). User is authenticated but doesn't have permission for the requested resource.

Security pattern: the page does NOT reveal what permissions the user has or doesn't have — this avoids leaking access control structure. Only generic explanation of possible reasons.

Common causes (listed):
· Page belongs to a different role (e.g. client trying to access /admin/*)
· Resource belongs to another workspace
· Permissions changed since last sign-in (session needs refresh)

Actions:
· Return to home (primary)
· Sign in with a different account (secondary)

Compliance: generic error message — does not expose role or permission details. Audit log records the access attempt for review.
Contact support →
403

Access denied

You don't have permission to view this page. This could be for a few reasons — your current account may not have the right role, the resource may belong to another workspace, or your session may need to be refreshed.

Common causes
  • You're signed in with a different role than the page requires
  • The resource belongs to another workspace (provider or client)
  • Your access was recently changed by your team administrator
  • Your session has expired — try signing in again

If you believe you should have access to this page, contact your team administrator or our support team.

← Index