9. Booking and courses
Modules: Booking, Courses
Two modules that share a shape: both let someone outside your organisation do something useful without an account.
9.1 Booking pages
Module: Booking
A booking page is your availability, published at a link. Someone opens it, picks a slot, books. No account, no email ping-pong.
What you configure: weekly availability windows in your own timezone, how long a slot is, buffer between bookings, minimum notice, and how far ahead people can book. The page can be public at a link, or internal-only for your team to book on your behalf.
What happens when someone books: available slots are computed on the spot — your windows, minus existing bookings and their buffers, minus anything too soon. They enter a name and email; the contact is matched or created. They get a confirmation email with a cancel link, through your organisation's own email account (chapter 5); without one the booking is made and kept, and the confirmation email is refused and logged on the contact. You get notified either way.
Two things are worth trusting rather than checking.
Double booking is impossible. Not "unlikely" — the database itself refuses two overlapping bookings for the same person, across all of their booking pages (the gap between bookings is kept by the application). If two people click the same slot in the same second, one of them gets it and the other is told to pick again. There is no window in which both succeed.
Daylight saving is handled. Your windows are local wall-clock times — "Tuesdays, 9am to 5pm" means 9am your time, in March and in November. The conversion is computed per date rather than with a fixed offset, which is the mistake that makes most booking tools shift by an hour twice a year.
Your team can also book internally on any page, for when someone phones instead of clicking.
Cancelling a booking. Cancel a booking from Bookings and the person who booked is sent a cancellation email, if the booking is still ahead, through your organisation's own email account (chapter 5), the same as the confirmation. Without one the email is refused and logged on the contact, so let them know yourself.
Deleting a page. A page with upcoming bookings can't be deleted: cancel those bookings first, or deactivate the page, which stops new bookings and keeps the ones you have. Once nothing is coming up, deleting the page also deletes its past and cancelled bookings, and the public link stops working.
9.2 Courses
Module: Courses
A course with enrolments, tracked through enrolled → in progress → completed, or dropped.
Marking someone complete emits course.completed, which is an automation trigger: tag
them, create a reminder, notify the team — and, through your organisation's own email
account (chapter 5), send congratulations or start an alumni sequence. The certificate
is issued by hand: Issue certificate appears on their row of the course page once the
enrolment is completed.
9.3 Certificates
Certificates are numbered per organisation, in order, and publicly verifiable. A number is never reused.
Issue one against a completed enrolment. Optionally email it to the graduate with a verification link, from your own email account (chapter 5). Without one, the certificate is issued all the same and the email is refused, with the reason. Anyone with that link — an employer, an admissions officer, a regulator — opens a public page showing the holder, the course, your organisation, the number and the date.
Nothing else leaks. The verification page shows what is needed to confirm the certificate is real, and nothing about your organisation, your other students, or the holder beyond the fact of the qualification.
There is a print layout.
A certificate issued by mistake can be deleted by an owner or admin, from the bin icon next to its number on the course page. Its verification link stops working straight away, and its number is not given to anyone else. The deletion is recorded in the audit log (Settings → Audit log) with the number. The enrolment stays as it was, so if it is still completed you can issue a new certificate, which gets the next number. If the enrolment itself was a mistake, delete the certificate first, then unenroll the contact.
Why this is worth more than it looks: a PDF certificate proves nothing, because anyone with an image editor can make one. A certificate that can be checked against the issuer in one click is a different object. If you train people, this turns your courses into something they can actually put in front of an employer.
