Create a course
A course is a sequence of pages with questions, always assigned to one client. This walks through creating one, filling it with pages, and publishing it so participants can start.
BEFORE YOU START
You need at least one client. Every course is assigned to one, and the Courses page will send you off to create a client first if none exists. If you also want the course to hand out a certificate, upload the client's certificate template before you get to the Certification section.
Create the course record
This part is deliberately short. You give the course a name and an owner, and everything else happens in the editor afterwards.
Open Courses from the sidebar and choose New Course.
Enter the Course Title and select the client under Assign to Client, then Create Course. Both can be changed later.
You land in the course editor, which has four tabs: Course Settings, Course Pages, Certification and Notifications. The rest of this article works through them in that order.
Fill in Course Identity
The Course Settings tab opens on Course Identity. These four fields decide how the course is labelled and which language participants see.
Write a Description. It's optional, but it's what someone reads before deciding to start, so write it for them rather than for your own filing.
Set the Public Language. This is the language of every learner-facing page — intro, questions and results. It is not the language of your dashboard.
Optionally give it a Category / Tag — Safety, Technical, Management. When the course sits in a bundle, courses sharing a category are grouped under that label.
Add pages
Pages are the course. Participants move through them in order, one screen at a time.
Switch to Course Pages and choose Add Page. Build the content in blocks — text, images, lists. Images come from the image library, so upload once and reuse them anywhere.
Repeat until the course is complete, then drag the pages into the right order and choose Save Order. Reordering is not saved automatically.
Each page carries a badge showing what kind it is:
Deleting a page asks for confirmation and cannot be undone, so if you only want it out of the way for now, move it to the end instead.
Decide what counts as passing
Back in Course Settings, the Completion & Scoring section controls the pass rule. There are two ways to set it, and they interact.
Leave All questions must be answered correctly to pass on for compliance-style training where a partial score isn't acceptable. Turn it off to allow a threshold instead.
Set Required Points to Pass. The editor compares your number with the total scored points in the course and warns you if it's higher — at that point nobody can pass.
Decide on Show answers on the results page. Off, participants see only their score — not which questions they got wrong. Keep it off if the same questions are reused across sittings.
A COMMON MISTAKE
If you add scored questions after setting Required Points, go back and check the number. It doesn't move with the total, so a course that was passable can quietly become easier than you intended.
Set access and lifecycle
Two fields here decide how long a completion is worth something, and how long you keep the record.
Then choose Save Course Settings. Each tab saves on its own, so save before switching.
Attach a certificate
On the Certification tab, pick the certificate issued on completion. Only templates belonging to this course's client appear in the list. If it says no certificates are configured, follow the link to set one up first — the course is fine to publish without one, and you can come back.
Participants who pass receive the selected certificate. Those who fail get nothing.
Optional: reminders and webhooks
The Notifications tab holds the email sent before a completion expires. Set Days Before Expiry and write the subject and body; leave the field empty and no reminder is ever sent. The available placeholders are {{first_name}}, {{last_name}}, {{course_title}}, {{expiry_date}} and {{course_url}}. This only works if Validity (days) is set — without it the section tells you so.
If another system needs to know about completions, add Completion Webhooks: an HTTP POST on pass, another on fail. Both are optional, both must be http or https, and they are dispatched in batches by a scheduled job rather than instantly.
Preview, publish, share
Choose Preview Course and walk the whole thing through, answering the questions as a participant would. No registration is needed and nothing is saved, so answer badly on purpose and check the fail path too.
Set the status to Published.
Share it. Use the public link for anyone who should register themselves, or generate an access link from the Results page for one named participant, which signs them straight in. Most often the course is simply added to a bundle instead, and participants reach it from there.
GOOD TO KNOW
Next time round, don't start from scratch. Clone course copies the pages and questions so you only change what's different — useful for a new year's version, or the same course for a second client.
If something isn't working
What next
A course on its own is rarely the finished job. Most people group several into a bundle, which is what participants actually log into and get assigned.