Roles and scenarios

Role	What they need to achieve	Typical pages
Project owner	Know what is configured, what is missing, and where risk exists.	Rollout overview, reporting, data fixes.
HR / L&D manager	Assign content, monitor completion, and communicate with learners.	Users, groups, content, reports.
Administrator	Manage users, roles, imports, and technical settings.	Imports, API, roles, audit.
Learner	Find and complete assigned content.	Sign in, my courses, certificates.
Integrator	Connect an external system.	REST API, webhooks, identifiers.

Common scenarios

Scenario	Primary role	Supporting role	Documentation path
Launch a new company space	Project owner	Administrator	Owner runbook -> Getting started -> QA and acceptance
Import or synchronize employees	Administrator	Integrator	Users and groups -> Client integrations
Assign mandatory training	HR / L&D manager	Project owner	Content and assignments -> Reporting
Verify rollout success	Project owner	HR / L&D manager	Reporting -> QA and acceptance
Investigate missing learning	Administrator	Internal support	Users and groups -> Content and assignments -> Architecture overview
Connect completion reporting to HRIS	Integrator	Project owner	Client integrations -> API and integrations

What each role should know

Role	Must understand	Does not usually need
Project owner	Ownership, rollout state, risk, evidence, escalation.	Rails models or serializer names.
HR / L&D manager	Content, assignments, deadlines, completion, certificates.	API request syntax.
Administrator	Users, groups, roles, imports, state changes, operational fixes.	Full internal assignment reconciliation details.
Learner	Assigned learning, progress, completion, certificate access.	Company-space settings.
Integrator	Identifiers, API auth, webhooks, retries, error handling.	Manual UI workflow details except for validation.

When a page serves multiple roles, the first paragraph should say who the page is for and what decision or task it supports.