PLATFORM CONCEPTS

Permissions are evaluated in context, not inferred from a page label.

A visible control does not itself grant authority. The responsible service validates authenticated and scoped authorization for protected operations.

View documentation

Before you begin

  • Defined roles
  • Active tenant or school context
  • Approved workflow responsibilities

Authorization inputs

The platform can evaluate signed identity, realm or application roles, tenant context, requested capability, record ownership, and workflow state. The exact policy belongs to the responsible service.

Least necessary access

Start with the minimum role and permission set needed for the user task. Separate creation, review, approval, publication, correction, and administration where the workflow requires it.

Troubleshoot access safely

Confirm the intended account, current institution context, assigned role, and task. Do not copy tokens into support messages. Provide the route, approximate time, and non-sensitive error reference instead.

Scope and limitations

  • Internal policy rules and privileged administration procedures are intentionally not public.

Related Anabhix guidance