How Lurno fits your context

Lurno is deliberately neutral: it gives you building blocks rather than a fixed template, so it works whether you’re training staff, teaching students, or educating customers. This page maps the platform’s ideas onto four common contexts. Most organizations recognize themselves in one of them — and many mix several.

Corporate & workforce training

You’re onboarding new hires, delivering compliance training, or upskilling teams.

• Organization → sub-organizations: model departments, regions, or business units as sub-organizations, each with its own people and settings. How many you can create is capped by your subscription, and the cap counts every organization in the tree.
• Groups: map to teams or job functions. Linking a program to a group enrolls every member, and people who join the group later inherit its programs automatically.
• Programs: onboarding paths, compliance courses, role-based tracks. Program types include self-paced, cohort, blended, event-led, pathway, and certification.
• Scheduling: use release windows and drip so a compliance course unlocks over time, and watch overdue required training on the enrollment hub’s attention rail.
• Assessments & certificates: prove completion of mandatory training and issue certificates with a public verification page.

Customer education (SaaS academies)

You’re a software or product company teaching customers to succeed with your product.

• Organization branding & custom domain: run the academy under your own platform title, logo, and theme, at your own web address, so it feels like part of your product.
• Enrollment access modes: open a program to anyone with the link, to anyone in the organization, or to specific people — invited individuals and groups only. Programs can also be set up so customers apply and you approve.
• Partner sign-on: your own product or portal can send an already-signed-in customer straight into Lurno without a second login. Turn it on yourself from Org settings → Integration with Enable partner integration — on your top-level organization; sub-organizations only get a read-only view of their own account code. You get an API key and an account code for every organization in the tree. The key is shown once — copy it then, because it can never be displayed again, and rotating to see a new one immediately kills the key your integration is already using. See Partner sign-on.
• Certificates: issue product certifications customers can share, with a public page anyone can verify.
• Insights: see participation, completion, and where learners stall. Insights is a module Lurno switches on per organization — see Plans, permissions & modules.

Higher education

You’re a university, college, or professional-education provider delivering courses and tracking outcomes.

• Programs → modules → lessons: structure a course the way faculty already think about it.
• Cohort programs & scheduling: run a group through a term on a shared schedule, with prerequisites gating which steps open next.
• Assessments: exams with a secure delivery mode and integrity events, portfolios, peer review, and rubric-based grading (analytic, holistic, or single-point).
• Competencies & frameworks: map learning outcomes onto a competency framework and track mastery across a program.
• Guardians: where relevant (younger or dependent students), give designated people scoped visibility of just their dependent.

Schools (K‑12)

You’re a school or district running classes, assessments, and reporting for students and families.

• Groups as classes: organize students into groups for classes or cohorts, and assign teaching staff by role. For larger structures you have two tools: branches model an operational tree inside one organization — campuses, departments, divisions — where a role granted at a branch cascades to the branches below it; sub-organizations are separate organizations with their own people, settings, and branding.
• Guardians: parents and guardians get their own dashboard, scoped to the dependents whose relationship has been verified.
• Scheduling & drip: release lessons on a timetable and set due dates on assessments.
• Assessments & grading: quizzes, exams, and human grading with feedback, routed through a single grading queue.
• Terminology: rename the platform words Lurno marks as customizable (for example what “programs” or “learners” are called), in singular and plural, per language — see Terminology.

The throughline

Notice that the features are the same across all four — only the configuration and vocabulary change. That’s the point: you set up the organization, the roles, the schedule, and the wording to fit how your context works, and the rest of this help center applies regardless of which row above describes you.

Not sure a specific capability is available to you? See Plans, permissions & modules.