Skip to content
LEAPDocs

Who it's for — the four roles

Four roles, four applications. What each one can see, do, and is accountable for.

How roles work

A role is a property of the account, not a mode you switch into. Signing in as a teacher lands you in the faculty application at /faculty; a student lands at /student. The navigation, the routes and the API permissions all follow from that one value.

Roles are enforced server-side, not just hidden in the interface. A student calling a teacher endpoint is rejected at the route, and every query is additionally scoped to the caller’s institution.

Teacher

The role that builds and delivers the course.

  • Creates courses, uploads syllabi and approves what extraction produced.
  • Runs the lesson workspace: plan, teaching script, materials, questions, transcript, recording, notes, attendance and downloads.
  • Authors assessments — quiz groups, the quiz builder, CSV question import, paper quizzes and rubric-based assessments.
  • Publishes Open Quizzes with public links for candidates outside the institution.
  • Reads class analytics and acts on them through remediation and Voice Feedback.

A teacher only sees their own courses and the sections linked to them. Cross-faculty visibility is an admin and management concern.

Student

The role the whole structure exists to move forward.

  • Sees enrolled courses and progress against the gate sequence.
  • Takes quizzes and exams — including locked-down exam mode with a server-side timer.
  • Receives remediation automatically when a gate is missed, drawn from that gate’s prerequisites.
  • Asks the AI tutor questions, which answers Socratically and refuses to run ahead of the gates the student has reached.
  • Reads generated study materials and a report card covering mastery, Bloom profile and attendance.

Admin

The role that makes the institution exist inside the platform.

  • Configures the institution: name, branding, subdomain, academic calendar.
  • Defines programs and subjects — the curriculum skeleton courses attach to.
  • Creates teachers and students individually or by bulk CSV upload, with validation before anything is written.
  • Manages sections and rostering, and links sections to courses.
  • Generates the timetable and resolves the conflicts it flags.
  • Runs the reports centre and absentee reporting.

Management

The role that asks whether any of this is working.

  • Faculty performance across sections and terms.
  • Student and faculty satisfaction, drawn partly from Voice Feedback transcripts.
  • Benchmarks between programs, departments and cohorts.
  • A report builder for questions the fixed dashboards do not answer.
  • Strategic decisions — a log of recommendations and the actions taken against them.

Management is read-heavy by design. It does not author content or edit rosters; it reads the institution and records decisions.

Who can do what

Create a courseTeacher. Admin can see them; management cannot edit.
Approve AI contentTeacher only, for their own courses.
Enrol a studentAdmin, via rostering. A teacher can add students to their own course.
Publish a public quiz linkTeacher.
Change institution brandingAdmin.
Generate the timetableAdmin.
See cross-faculty analyticsAdmin and management.
Take an assessmentStudent, and unauthenticated guests on an Open Quiz link.