Internal knowledge has nowhere to live.
Onboarding playbooks, product training and internal process docs sit in slide decks and shared drives, disconnected from the learning your people actually track.
Harmoni Studio
Build the training only your company needs.
The library covers what every company needs. Studio covers what only yours does: your policies, your equipment, your induction. It is a block editor rather than a slide deck, and what it publishes obeys the same audience rules as every other course in Learn.
- Interactive by default: scenarios, branching, simulations, sorting and hotspots, not slides with a quiz bolted on the end.
- Bring what you already own: a SCORM package or an LTI tool drops in as a block beside everything else.
- Preview it as a learner sees it, before a single person is enrolled.
- Publish straight into the Learn catalogue, setting mandatory training, due date and audience as you go.
- Licensed per authoring seat, so only the people who actually build courses need one.
- HeadingHandling a difficult call
- VideoWhat good sounds like
- Branching scenarioThe customer escalates
- Knowledge checkWhich reply de-escalates?
- Drop block here
Add a block
- Simulation
- Flip card
- Sorting activity
- Hotspot question
and the rest of the catalogue
Preview as a learnerExactly what they will see, before anyone is enrolled
Publish into LearnStraight to the catalogue, no import step
Or start from a draftHARMONI AI writes the first version · add-on
Courses that take months
Off the shelf training never quite fits.
Building courses means another tool.
Authoring platforms live outside the HRIS, so a course built elsewhere has to be re-imported, re-assigned and re-tracked by hand.
Licensing is all or nothing.
Most authoring tools charge per editor seat company wide, even when only one or two admins ever build content.
Inside the workspace
One seat writes. The company takes the course.
Canvas, preview and publish share the same course. A first draft is an add-on. Nothing here is a second LMS.
The editor
Canvas
A lesson is a stack of blocks, not a slide deck with a quiz bolted on the end.
- Heading, video, branching and a knowledge check sit on one canvas and move when you drag them.
- Scenarios, simulations, sorting and hotspots are blocks, not a second product.
- A drop zone waits for the next block. The lesson renumbers itself around it.
- One authoring seat writes. The rest of the company takes the course in Learn.
One record. Nothing entered twice.
Studio does not live on an island.
Studio is the authoring layer for Learn. Courses built in the studio publish directly into the Learn catalogue and inherit the same role, grade and mandatory training rules as every other course.
Inside Studio
Every capability, on the same record.
Why teams switch
Authoring that refuses to miss a clause.
The same blocks the learner sees.
Headings, knowledge checks, walkthroughs and the rest play in Learn with the same grading. Studio is not a preview of a different product.
Coverage is a publish gate.
A policy document is split on its numbering. Each uncovered clause is its own issue. A pretty course that dropped 7.3 will not ship.
A seat is a seat.
Library and Builder are gated on Studio seats. The rest of Learn stays open. We do not pretend every People admin is an author.
A package is a block.
A SCORM package or an LTI tool drops in beside a knowledge check. There is no side door that bypasses the canvas or the audience rules.
Already connected
Published here, assigned there.
A Studio course is a Learn course. Assigning, due dates, certificates and policy acknowledgements all read the published version, not the draft on your canvas.
- Guided walkthroughs are drawn on real screenshots. The generator cannot invent them, because a model has never seen your software.
- Captions transcribe first, then translate. A track that shifts by one line is refused rather than timed wrong.
- Image search ends on Openverse, restricted to public domain and CC0, so a credit line never has to survive every export.
- SCORM upload is a real package, not a “coming soon” picker.
Who it is for
The people who actually write the course.
The author
The person on the canvas.
Felix builds a policy course from the uploaded Word file. Coverage names the clause that is still missing.
L&D
The person who publishes.
Publish is blocked on the same issues the checklist shows. There is no second opinion that says it is fine.
The learner
The person who will be tested.
A knowledge check they fail twice reveals the answer. A walkthrough with no recorded result says so.
People
The person who needed the policy read.
They assign the published course. Acknowledgement waits on completion, not on a tick in a register.
Keep reading
How a course should be built.
Questions people actually ask.
Can Studio AI write a walkthrough of our software?
No. That block is absent from the generator on purpose. A model has not seen your screens. You record them.
What stops a course missing a clause?
Coverage is a publish blocker. Each uncovered clause is its own issue, named by number. A percentage would hide the miss.
Who is allowed to author?
People with a Studio seat. Library and Builder are gated. The rest of Learn is not.
Do captions invent English from Arabic audio?
They transcribe in the spoken language first, then translate the text. A shifted line count falls back rather than mistime the track.
Studio pricing
One module. One honest price.
No tiers to decode and no sales call to get a number. Slide to your size and see exactly what Studio costs.
Studio needs Learn
Studio makes the courses.
Learn is where they live.
Studio is an add-on to Learn rather than a product of its own, because a course with nowhere to be taken is not worth building. Learn brings the catalogue, the audiences, the reminders and the reports. Studio adds the ability to write your own.
Add intelligence with HARMONI AIAvailable as an optional add-on. Studio is complete without it; switch it on when you want drafted documents and cited answers here too.Explore the add-on →
Ready to bring Studio
into your workspace?
Every workspace starts from the connected employee record. Add Studio the moment your team needs it, with no re-import and no separate setup.