Modules and screens
The back office module by module: what each one is for, who works in it, which records it owns and every screen it contains. Screen lists are read from the navigation contract, so they always match the prototype. Modules added or extended in the revision of 5 October 2026 show their source requirement and whether they add scope.
| Module | Group | Purpose | Primary users | Revision 5 Oct 2026 | Screens |
|---|
Added inside existing modules
Capabilities of this revision that live in a module that already existed. They have no menu group of their own; each lists its purpose, key screens, source requirement and scope treatment.
Outside the modules
Command center
The first screen for staff: this week's batches, seats, money in, what is at risk. Reads from every module, owns nothing.
Tasks and approvals
One queue for everything that waits on a person: discounts, refunds, certificates, payouts, AI drafts.
Portals
Learner, instructor and corporate portals are views on the same records with a narrower permission set, described under roles and access.
Partner portal
A partner organisation sees its own deliveries and settlement lines and nothing else. Scope is shown by static hiding in the prototype, not enforced authorization.
My HR self-service
Every employee's own leave, requests and pay summary. Reads People and HR, owns nothing.