Most LMS platforms have two roles and a lot of workarounds
Teacher and student covers about a third of the people who need access. The rest — teaching assistants, graders, course builders, department heads, parents, observers, support staff, external moderators — end up sharing logins or getting far more access than anyone intended.
✗The two-role problem
- A teaching assistant gets full instructor access because there is no other option.
- Parents and observers either see everything or nothing at all.
- Course builders need an administrator to publish, so publishing becomes a bottleneck.
- Department-level reporting means exporting everything and pivoting it by hand.
- Security settings live in a configuration file nobody has opened since implementation.
✓Thirteen roles, properly scoped
- System, institution and department administrators each get a dashboard scoped to their level.
- Instructor, teaching assistant, course builder and grader are separate profiles with separate permissions.
- Parents and observers get a read view of exactly the learner they are entitled to see.
- Analytics roll up by course, department and institution without an export.
- Security posture is a panel on the dashboard — hashing, lockout, timeout, MFA, self-registration, audit.
One platform, thirteen different products
The same system looks completely different depending on who signs in — which is the point.
Thirteen roles, from the sign-in screen onward
System administrator, institution administrator, department administrator, instructor, teaching assistant, course builder, grader, student, parent, observer, support and guest. Each has its own navigation, permission set and landing dashboard. The role is not a checkbox on a user record — it is a distinct experience of the product.
System administration with the security posture in view
Active users, students, live courses and pending requests, alongside a recent authentication activity stream and a security posture panel that states the position on password hashing, minimum length, account lockout, session idle timeout, MFA, self-registration and the hash-chained audit log. Every one of those is a setting, shown where the decision gets made.
Institution administration with a real hierarchy
Users, courses, hierarchy, enrolments, terms, categories, branding, authentication, security, analytics, integrations, audit log, competencies, accessibility, standards and interoperability, AI Studio and extensions — scoped to the institution. A department administrator sees the same shape of screen, bounded to their department.
Course analytics that name the students at risk
Students, mean score, submission rate and awaiting-grading across an instructor’s courses, with grade distribution flagging at-risk learners, average completion by course and a fourteen-day submission trend. The point of the screen is the red flag on the left, not the averages.
Delegated teaching, properly bounded
The teaching assistant profile: their courses, their students, their tasks and their marking queue — with gradebook, attendance, groups, discussions, reports and messaging, and nothing else. Delegation stops being a permissions compromise and becomes a designed role.
Take the full tour
Five screens across four different roles.
An LMS with the ERP already attached
Courses and learning modules
Structured modules, a content collection, course tools and a builder role that can publish without administrator rights.
Gradebook and rubrics
Weighted grading, rubric-based marking, delegated grading and an explicit awaiting-grading queue.
Assignments, tests and banks
Question banks per course, reusable across assessments, with attempt controls and release rules.
Attendance and groups
Attendance capture, group management, discussions, announcements, messaging and a shared calendar.
Competencies
Competency frameworks mapped to activities, so completion means demonstrated capability rather than time served.
Standards and interoperability
Built to interoperate with the standards your other systems already speak, so the LMS is not an island.
Parents and observers
A read-only view of one learner’s progress, attendance and results — entitled, scoped and audited.
AI Studio
An institution-controlled space for AI-assisted content and feedback, with the governance settings held by the administrator.
Integrations, API and OAuth
A documented API with OAuth so enrolments, results and rosters move between the LMS and your student system automatically.
Security you can read off the dashboard
Every setting below is displayed as a posture panel on the administrator dashboard, because a control nobody can see is a control nobody maintains.
From procurement to first term
Structure
Your institution, departments, terms and categories are configured, and the four-level hierarchy is set to match your organisation chart.
Roles
The thirteen role profiles are mapped to your real job titles, and permissions are tuned where your governance differs from the default.
Migrate
Courses, enrolments, historic results and content are imported, and integrations to your student system are connected over the API.
Launch
Instructors and teaching assistants are onboarded into their own scoped views, with analytics live from the first assessment.
Straight answers
Because that is how many distinct relationships people actually have with a course. Teaching assistant, grader and course builder do genuinely different jobs from an instructor, and parents and observers need a bounded read view. Collapsing them forces over-permissioning, which is the most common security finding in an LMS review.
It carries the ERP layer — organisations, hierarchy, terms, enrolments, categories, competencies and reporting — so many institutions run it as the system of record. Where a dedicated SIS already exists, the documented API and OAuth integration keeps rosters, enrolments and results synchronised in both directions.
It is an institution-controlled space for AI-assisted content authoring and feedback, with the governance settings — what is enabled, for whom, and on what content — held by the institution administrator rather than by individual instructors.
As a distinct role profile, entitled to one learner and scoped to a read view of that learner’s progress, attendance and results. Access is granted deliberately, bounded by the entitlement, and recorded in the audit log like any other access.
Accessibility is a first-class administration area within the platform rather than a compliance checkbox, covering the learner, instructor and administrator experiences. We will walk your team through the current conformance position against your specific obligations during evaluation.
See it from every role in one sitting
The fastest way to evaluate this platform is to sign in as four different people in twenty minutes. We will run that session with your own course structure loaded.