Skip to content
Help

What is Lurno

Lurno is a platform for building learning and running it for a group of people. A software company uses it to train customers; a business uses it to onboard and upskill staff; a university delivers courses and tracks outcomes; a school runs classes, assessments, and reports for families. The same building blocks serve all of them — you configure them to fit your context.

The shape of the platform

Section titled “The shape of the platform”

Everything in Lurno hangs off a small number of ideas. Once these click, the rest of this help center is just detail.

  • Your organization is your space on Lurno. It has its own people, content, branding, and — if you set one up — its own web address. If you run several distinct units (campuses, departments, regions, reseller accounts) you can create sub-organizations underneath it. Separately, branches model an operational tree inside one organization, where a role granted at a branch cascades to the branches below it.
  • People join your organization and hold roles, which carry permissions that decide what they can do. You can gather people into groups (a class, a cohort, a team, a department).
  • Programs hold your learning: a program contains modules, modules contain lessons, and lessons contain content blocks. A program can be self-paced, cohort-based, blended, event-led, a pathway, or a certification. Reusable material lives in the Library, and reference documents live in Sources.
  • Enrollment connects people to programs: who is taking what, in what role, and whether they were added directly, invited, applied to join, or joined an open-access program themselves.
  • Scheduling controls when content becomes available — schedules and release windows, drip, prerequisites, drop policies, and holidays.
  • Assessments measure learning — quizzes, exams, surveys, portfolios — with grading, feedback, and analytics.
  • Outcomes are what learners walk away with: certificates, each with a public verification page anyone can check, and competencies they’ve demonstrated.

Who operates Lurno

Section titled “Who operates Lurno”

Lurno ships a set of system roles — an organization administrator, an instructor, a learner, a plain member, and a handful of staff roles for people who mentor, facilitate, or review. Inside an organization those system roles are read-only: you can open the permission grid and see exactly what each one is allowed to do, but you can’t change it, because it applies to every organization on the platform. What you can do is add your own custom roles — blank or cloned from an existing role — and tune their permissions.

Because roles are named and shaped differently in every account, this help center describes what a task needs in plain words — “requires permission to update the organization” — rather than naming a job title.

Broadly, three kinds of people use the admin side of Lurno:

  • People who set up and administer the organization (branding, domains, people, roles, integrations).
  • People who build and deliver learning (programs, content, assessments, grading).
  • People who take the learning — learners, who get their own streamlined experience separate from the admin area.

A note on wording

Section titled “A note on wording”

Your organization can rename many of the words you’ll see in the product. Lurno publishes a glossary and marks which of its terms an organization is allowed to customize; those can be overridden, in singular and plural, per language. Where a term is commonly customized, this help center uses Lurno’s default name. If a label in your account doesn’t match what you read here, check Terminology — an administrator may have renamed it.

Where to go next

Section titled “Where to go next”