Skip to main content

Users, roles & permissions

What it does​

This is where administrators control who can sign in and what each person is allowed to do. Access is built from roles (job-based bundles of permissions), permissions (individual allowed actions), and policies (contextual rules), plus scopes that limit a person to certain organizations or facilities.

Where to find it​

Administrators work under Admin → Access:

  • Users — /admin/access/users
  • Roles — /admin/access/roles
  • Permissions — /admin/access/permissions
  • Policies — /admin/access/policies

📸 Screenshot: the Users admin list (access-users).

Common tasks​

Add a user and give them access​

  1. In Users, select New, enter the person's details, and Save.
  2. Assign one or more roles to grant the permissions they need.

Set what a role can do​

Open Roles, choose a role, and adjust the permissions it includes. Everyone with that role is affected.

Limit a user to certain organizations or facilities​

Open a user and manage their scopes (/admin/access/users/[userId]/scopes) — or a provider's scopes (/admin/access/providers/[providerId]/scopes) — so they only see and act within those places.

Add a contextual rule​

Use Policies for rules that depend on context (beyond a simple role), such as conditions on when an action is allowed.

Tips & limitations​

  • Prefer granting access through roles rather than one-off permissions — it's easier to manage and audit.
  • Access is enforced server-side and at the record level: users only see the data their roles, scopes, and consent rules allow — see Visibility & consent.
  • Removing a role or scope takes effect immediately.