Teach your customers on your own domain, not a vendor's.
An academy that looks like your product, signs your customers in from inside it, and issues certifications an employer can check.
What a product academy needs that a course tool does not
Customer education runs on somebody else's login. Your users already have an account with you, so the academy has to accept that account rather than ask for a second one, answer on a hostname you control, and report by customer rather than by class. Lurno does all three from one tenant: partner sign-on hands over a learner your product has already authenticated, each customer can be its own sub-organisation with its own domain and brand, and nearly every reporting measure splits by organisation. Certifications are checked at a public URL that needs no account.
- Customer education
- Training a company runs for the people who buy and use its product: onboarding accounts, certifying power users, training partners, taking load off support. It differs from internal training in who the learner reports to — nobody in your company. So it belongs under your brand, behind your login, not a new one.
A corporate academy on Lurno runs training for 15 client companies from one tenant, each client a sub-organisation with its own people and programmes. Swap clients for accounts and classes for product tracks and you have a product academy. What differs is the front door.
How a customer gets from your product into a course
Five hops, one of which is a redirect. Your learner sees none of them.
- 01
Your backend signs an assertion
A signed-in user clicks Academy in your product. Your server mints a short-lived compact JWS, signed with HMAC-SHA256: the user's id in your system, their email, an optional name, an expiry and a one-time id.
- 02
It travels server to server
Your backend posts it to Lurno directly. The assertion never touches the browser, so your customer's email and name never land in a URL, a history entry or a referrer header.
- 03
Lurno verifies before anything else
The signature is checked against your key, held in a vault. Lifetime is capped on our side, so a far-future expiry written into the assertion cannot extend it. The one-time id is checked against ids already redeemed, closing the replay window.
- 04
A single-use code comes back
Lurno attaches the person to the right organisation as a learner — a partner key cannot mint an administrator — and returns a URL on that organisation's own hostname, carrying a code that expires in two minutes.
- 05
They land signed in
The page strips the code from the address bar before exchanging it, swaps it for a real session, and puts the learner in their learning. No login screen, no password, no second account.
Yours down to the favicon
It answers on learn.yourcompany.com
Point a hostname at Lurno, publish the records it shows you, and the certificate issues on its own. Every organisation in your tree can hold one. The login page resolves logo, title, theme and background from the hostname before anyone authenticates, so the first screen a customer sees is already yours.
- Colour tokens, both fonts and the corner radius are yours, with a light logo and a dark one. Rename the vocabulary per organisation and per language — teacher becomes coach, class becomes cohort.
A credential your customer will put on LinkedIn
A definition says what the credential means — perpetual, valid for a number of days, expiring on a date, or renewable. A rule says what earns it: finishing a track, passing an assessment, scoring at or above a mark. Issuance is enforced once per definition and learner in the database, so a re-run never sends a second copy.
- Each credential carries a serial, a public link and a QR code on its PDF. All three reach one page that answers valid, revoked, expired or not found — no account, no sign-up wall, and on a verified domain it sits on your host.
Answers to *which account*, not just *how many learners*
Reporting is a semantic layer: certified measures, each with the dimensions it may be split by. Organisation is one of them on nearly every measure, so completions, attempts and enrolment states break down by customer. A question asked in plain language compiles to a validated query against those same measures. Switched on per organisation.
Reporting and analyticsThree ways to gate a course
Set a default for the organisation, then override it per offering. All three run side by side, so your free product tour and your partner certification track live in one academy.
| Capability | Public | Organisation | Restricted |
|---|---|---|---|
| Who can take it | Anyone with the link | Any member of that organisation | Invited people and named groups only |
| Needs an invitation | No | No | Yes |
| How the learner usually arrives | A link on your site or in a help article | Partner sign-on, from inside your product | An invitation to a person or a group |
| Typical use | A product tour or a free 101 | Anything a customer's staff may take | A partner track, a beta, a cohort you sold |
| Seat limit, waitlist and capacity quotas | Yes | Yes | Yes |
Access mode decides who may enrol; it does not create accounts. Learners arrive today by invitation or through partner sign-on — self-serve signup is in development.
What a product team asks about next
The tools you already build with
Figma, Notion, Airtable, Canva, Miro, CodePen, Typeform and the Google editors each have their own embed type. A Zoom, Teams or Meet link is a lesson resource — Lurno does not host the call.
Email that comes from you
Notifications can send from your own subdomain, so the invitation to your certification track is not signed by a vendor your customer has never heard of.
Payments and checkout
In developmentDesigned, not built. Charge for a certification today by taking the money in your own billing system, then enrolling the buyer by invitation or partner sign-on.
SCORM, xAPI and LTI 1.3
In developmentModelled in the product; the runtime is in development. If a customer's IT team wants your course as a package inside their own LMS, tell us early.
Where this connects
Before you scope the integration
Bring us the button in your product.
Show us where Academy would sit in your navigation. We will walk the sign-on hop, the hostname and the credential a customer ends up holding.