Every role gets a direct destination and a clear data boundary.
The navigation model groups work by role, while policies, academy scope, ownership, and enrollment checks continue to make the final authorization decision.
Supported roles
| Role | Primary destination | Owns | Visibility boundary |
|---|---|---|---|
| Admin / Super Admin | /dashboard/system | Platform health, tenancy, security, settings, and connected operations. | Platform permissions and tenant rules. |
| Academy Admin | /dashboard/academy | Academy operations, learners, course quality, staff access, and commerce context. | Selected academy and assigned permissions. |
| Instructor | /dashboard/teacher | Owned courses, Course Studio, assessment work, planning, and learner support. | Editable/owned courses and permitted academy records. |
| Reviewer / Moderator | /dashboard/reviewer | Approvals, question review, moderation, and assigned checks. | Review/moderation permissions only. |
| Support Staff | /dashboard/support | Access issues, payments, certificates, notifications, and activity investigation. | Support permissions and scoped records. |
| Student | student.dashboard | Personal learning, calendar, assessments, resources, notes, tutor, and completion. | Own active/completed enrollments and learner-owned records. |
| Parent / Guardian | student.companion.index | Read-only linked learner progress and permitted supporting information. | Active guardian observer links. |
| Corporate Manager | student.companion.index | Read-only linked learner progress and permitted team learning visibility. | Active corporate-manager observer links and payment flag. |
Route-family ownership
Public and access
academy.storefront.* and course-invitations.* describe catalog discovery and invitation acceptance. They never expose protected curriculum just because a course page is public.
Operations and authoring
lms.courses.*, lms.calendar.*, lms.boards.*, and lms.assessments.* stay behind authenticated permissions and academy ownership.
Learning
student.* routes resolve student or companion experience based on role and relationship. Course and content access remains enrollment scoped.
Intelligence and administration
Reports, automations, AI, commerce, settings, roles, and security use their existing permission policies and product navigation visibility.
Implementation rule: navigation is an affordance, not authorization. Any new endpoint must still validate role, permission, academy, ownership, related-record scope, and the underlying course or learner access rule.