​

Role permissions

Veridian Motion uses role-based access plus row-level security (RLS) scoped by facility membership. Permissions below describe the built matrix; multi-facility switching and some program modules are rolling out — confirm activation for your deployment.

​

Staff roles

Patient kiosk access is separate (Patient ID + PIN) — not a staff role.

​

Permission matrix (core)

* bh_clinician permissions apply only if/when a Behavioral Health module is legally cleared and enabled for a deployment. No public BH product docs.

​

Role summaries

​

Physical therapist (pt)

Primary clinical user. Reviews assigned MSK assessments, Precision Rehab session logs / routine completions, and Medical Intake flags. Approves plans, notes, messages patients. May assign Chess activities per facility policy.

​

Administrator (admin)

Operational owner — bulk roster import, program entitlements and seats, bulk/per-patient enrollment, roles, MFA reset, Communication Record, admin analytics, legal-forms console, billing snapshots.

​

Officer (officer)

Facility operational support per agency policy. Does not receive clinical PHI by default.

​

Warden (warden)

Operational visibility only — enrollment counts, workflow activity, safety escalations. No clinical PHI. HIPAA minimum-necessary by design.

​

IT admin (it_admin)

Technical administration — security settings, compliance tooling, MFA break-glass.

​

BH clinician (bh_clinician)

Role key reserved for future BH workflows. Behavioral Health is not a public product pending WOPR legal clearance — see Roadmap.

​

Wellness participant (wellness_participant)

Access to the confidential Officer & Staff Wellness portal as an employee participant.

​

Patient (kiosk)

​

Enforcement

1. Application UI and API — role checks
2. Row-level security — facility-scoped queries
3. Hash-chained audit log — sensitive actions; Communication Record access logged
4. Program entitlement checks — seat-capped enrollments

​

What’s next