One platform, a branded academy for every client.
You sell learning to other organisations, and each wants its own logo, domain, administrators and numbers. Lurno gives every client a full organisation inside your tenant, and leaves you one programme to maintain instead of fifteen.
How a training provider runs many clients on one platform
A training provider gives each client company its own sub-organisation inside a single Lurno tenant: its own members, administrators, programmes, branding, vocabulary and custom domain, with certificates and reporting scoped to that client alone. You operate all of them from one account. A programme authored once in your own organisation is then shared into every client — read-only and live, so a correction reaches all of them at once, or forkable, so a client gets an editable copy it owns. One corporate academy runs training for 15 client companies this way. A K-12 publisher runs 114 schools.
- Client academy
- A sub-organisation you operate on behalf of a customer: its own logo, colours, wording and domain, its own administrators and learner directory, reporting on its own people only. They nest, so a client with three regional entities is three children beneath it.
Separation is enforced underneath the platform, not by hiding buttons: separation built into the platform itself decide what a request may read before anything on top of it runs. Roster permissions — editing a member, seeing personal data, reading an audit log — do not cascade from a parent into a child, so a client's training lead can administer their own academy without you gaining standing power over their staff.
Author once. Deliver fifteen times.
One master programme, shared into every client
Your programmes live in your own organisation. Grant a client view access and they run the live programme read-only: you fix a lesson, and the fix is theirs the same day. Grant duplicate and they fork an editable copy they own. With no grant, it is invisible to them.
- A fork runs as a job you watch by phase — modules, blocks, outcomes, competencies, assessments — so a three-year syllabus copies without a spinner.
- Revoke access and the programme leaves that client's catalogue. Forks stay with the client who owns them.
Intakes, seat caps and what has to come first
Every enrollable thing carries an offering: a seat cap, an access mode and a schedule. Schedules come in five shapes — no dates, fixed, rolling, drip and cohort — set on the thing itself, on a cohort, or on one learner's enrolment. Fill a cohort and the next registration is waitlisted.
- Prerequisites are boolean sets with AND and OR: a completion, a score above a mark, time served since enrolment, a date, group membership, a concurrent enrolment, or a named person's approval.
Your staff, their staff, nobody else's learners
Custom roles are assembled from a permission catalogue and granted at a scope: an organisation, a sub-organisation, a programme, a cohort, a course, a group or a branch. A role granted at a branch cascades down every branch beneath it. A client's administrator is granted inside their organisation and sees nothing beside it.
- Access reviews and an audit log that cannot be quietly edited record who granted what, and when — the evidence a client's auditor asks for.
Four steps to a live client academy
Done from your own settings. No ticket, no engineer of ours.
- 01
Create their organisation
One action bootstraps the child: the organisation record, your membership, an admin role for its creator, and a default audience group.
- 02
Brand it, point the domain
Set colours, fonts and radius, add a light logo and a dark one, rename the vocabulary per language. Point learn.theirbrand.com at Lurno; the certificate issues itself.
- 03
Share what they bought
Grant view or duplicate access, programme by programme. Their catalogue fills with nothing re-uploaded; what they did not buy stays invisible.
- 04
Enrol, schedule, hand over
Invite or bulk-enrol their people, set the seat cap, attach the schedule, hand their administrator the keys.
Selling to fifteen companies is a different shape
Creator platforms are built for one business selling courses to consumers, and they are good at it. Selling accredited training to other organisations is a different shape — and there is one row they still win.
| Capability | Lurno | A creator platform |
|---|---|---|
| A branded academy per client | A sub-organisation per client, nesting as deep as your structure needs | One business, one brand, one audience |
| Its own domain and login page | A domain per organisation, TLS automatic, login page resolved from the hostname | A single site and domain |
| Roles that follow a hierarchy | A role granted at a branch cascades down every branch beneath it | No organisation tree for a role to travel through |
| Accreditation and competencies | Frameworks with evidence, automatic mastery and re-certification windows | Not part of the product |
| Assessment depth | 19 question types, 7 assessment types, three rubric kinds, peer review, psychometrics | Quizzes, aimed at completion |
| Credentials a third party can check | A serial, a QR code and a public verification page on your client's domain | Completion certificates |
| Checkout and paymentsThe honest row. If card checkout to consumers is your business, a creator platform is the better tool right now. | In development. Today you invoice the client and enrol their people | Built in, and the core of the product |
Competitor facts come from published pricing and product pages, each with the date it was checked. Full write-up: Lurno vs Kajabi.
What a tender asks for
SCORM, xAPI and LTI 1.3
In developmentModelled in the product; the runtime is being built. If standards conformance gates a tender you are bidding for, say so on the call.
Payments and checkout
In developmentDesigned, not built. No card checkout, no self-serve signup — you invoice the client, and accounts are created by invitation.
Where this connects
Before you move your client list
Bring us your client list.
Fifteen companies, four brands, one accredited programme, a domain each. We will model the tree on the call and be straight about what is not built yet.