Required training, real due dates, and a record that survives an audit.
Departments and regions become branches. Teams and job functions become groups. Client companies become sub-organisations with their own logo, domain and administrators. A corporate academy runs training for 15 client companies from one tenant this way.
What corporate training on Lurno looks like
Lurno runs corporate and workforce training from one tenant that holds every part of the business you train. Departments and regions are branches, where a role granted at a branch cascades down every branch beneath it. Teams and job functions are groups, and a group is what you assign training to. Client companies and subsidiaries are sub-organisations, each with its own directory, branding, domain and administrators. An enrolment can be marked required, given a due date and a recertification interval, and made visible to the learner's manager. Overdue required training then surfaces in three places: the attention rail on the enrolment hub, each manager's team page, and a certified overdue-compliance report.
- Required training
- An enrolment flagged as required — an obligation with a date on it, not a course somebody may take. It carries a due date, an optional recertification interval, whether the manager may see it, and whether the learner may withdraw. A named compliance policy holds that recipe once, for every course that shares it.
The modelling is one decision, repeated: which of three primitives a division belongs in. Branches are for authority — a director given a role at Northern Europe holds it at every office beneath it, ten levels deep. Groups are for assignment: Field Engineers, the January intake, everyone in Payroll. Sub-organisations are for separation — a client company whose administrators must not see the parent's roster. The three compared in full.
Groups need not be kept by hand. A rule matches on role, branch, another group, account status, last activity or a custom field of your own, refreshes every five minutes, and tags the members it added — so a person you added by hand is never removed by a rule.
Assign it, chase it, renew it
Assign to a group, not to a list of names
Pick a group, add a few people who are not in it, exclude a few who are, choose one course or six, then set the terms: required or not, a due date, a recertification interval, whether the manager sees it.
- Each row succeeds or fails on its own, and rows that stop say why — at capacity, consent missing, approval outstanding. An administrator may override a gate, but only with a written reason that writes its own audit row.
What is late, on the page you already open
The enrolment hub opens on a needs your attention card: applications waiting on a decision, seat offers expiring within 24 hours, overdue required training, courses close to full. Each row is a count and a way into the list behind it.
A manager sees their own people, and only their own
A My team page lists required training for the people a manager is the manager of record for — overdue, due within seven days, in progress, completed. The relationship is verified and can expire, so it lapses when the employment does.
Training that comes back round on its own
Set a recertification interval and a daily job does the rest: a due-soon event, then an overdue one, de-duplicated so nobody is reminded twice in a day. When the interval elapses on a completed enrolment it creates the next one.
How certificates are verifiedSCORM, xAPI and LTI 1.3
Modelled in the product; the runtime is being built. If a course library you already own has to run on day one, say so on the call.
How an academy with fifteen client companies is set up
One tenant, one content library, fifteen separate front doors.
- 01
The academy sits at the top
Its organisation holds the programmes, the question banks and the certificate definitions. Author once, here.
- 02
Each client becomes a sub-organisation
Fifteen children, each with its own members, roles and administrators. Roster permissions do not cascade in from the parent, so appointing a client's administrator hands the academy no power over that client's employees.
- 03
Each client gets its own front door
A logo pair, fourteen colour tokens, a font, a corner radius, and a domain of their own with TLS issued automatically. Employees meet their own company's login page — or, with partner sign-on, none at all.
- 04
Inside a client, the org chart takes over
Departments become branches, teams become groups, and the client's training manager holds a role at their branch that cascades down it. The academy still sees the whole tree.
Lurno, and one LMS instance per company
What decides this category is what happens when you take on a sixteenth company.
| Capability | Lurno | An instance per company |
|---|---|---|
| Taking on another company | An admin creates a sub-organisation, inside the plan's limit | A new instance, contract and configuration |
| Where the content lives | One library at the top, shared or deep-copied into any organisation in the tree | One copy per instance, kept in step by hand |
| Own branding and domain per company | Yes | Commonly one brand per instance |
| How far a client's administrator reaches | Their own organisation; roster permissions do not cascade in from the parent | Whatever that instance's roles allow |
| SAML or OIDC single sign-on | On the roadmap, not built | Commonly available |
The right-hand column describes the common shape of a per-company deployment, not any one product. The last row is the honest cost of choosing us today: if directory-backed sign-on or a SCORM library gates the rollout, that is a real reason to buy elsewhere.
What a compliance officer is actually asking for
Quarterly access reviews, signed off
A sweep snapshots every active role assignment per organisation each quarter: who holds what, at which scope, granted when and by whom. An officer attests with a note, and the attestation is itself an audit event.
Where this connects
Before the procurement call
Bring us your org chart and your compliance matrix.
Fifteen client companies, four regions, a course everyone redoes every year. We will model it on the call.