Waivers
Write the waivers guests, students, and new members sign at registration, publish new versions, and review who signed what.
Zeil asks people to sign a waiver when they register — guests before their spot on a sail is confirmed, (optionally) students when they register for a course, and (optionally) new members when they accept an invitation to join the club. As an admin, you control the wording of all three under Admin → Waivers.
There are three waivers, one per flow:
Guest sails
Signed by invited guests before their spot on a sail is confirmed.
Course registration
Acknowledged by students when they register for a course.
Club membership
Signed by invited members when they accept their invitation and join the club.
Defaults
Until you publish your own, the guest sail waiver shows Zeil's built-in default text (labelled v1). The course and membership waivers are opt-in: if you never publish one, course registration requires no acknowledgement, and invited members join without signing anything.
Writing and publishing
Open any of the waivers to edit its title and text. The text is Markdown — headings, lists, and links all work — and is shown exactly as written to everyone who registers.
When you're happy, hit Publish. Publishing creates a new version (v1, v2, …), and from that moment new registrations sign the new text.
Versions are permanent
You can't edit a published version — "editing" always publishes a new one. That's deliberate: people who already signed keep a record of the exact text they agreed to, which only new registrations move past. Publishing a new version does not ask existing guests, students, or members to sign again — a membership waiver only applies to people joining from that point on.
If someone has a registration page open while you publish, their signature on the old text is refused — they're shown the updated waiver and asked to read and sign again.
Version history & signatures
Each waiver's page shows:
- Version history — every published version, when it went live, and how many signatures it collected.
- Recent signatures — who signed, with their name, email, when they signed, and which version they agreed to.
Every signature is stored with a snapshot of the exact text that was signed, so the record stands on its own — even if the sail, the enrollment, or the signer's account is later removed. Publishing a version and every individual signature also appear in the audit log.