Create waivers, terms and acceptance rules

Waivers can hold an indemnity, code of conduct, terms of use or optional consent. JollyBee records who accepted which version and when; it does not turn the document into a drawn electronic signature.

Create the document

Open Admin → Waivers → New waiver and add:

• A member-facing name.
• A stable internal slug that identifies the document across versions.
• The complete document body.
• Whether it is generally required or optional.

After creation, set Where this applies. A document can apply to everyone on the community's books, at signup, to an entire access type, or to selected offerings. The same document can have more than one scope. It can also be shown without blocking progress for optional consent.

There is no separate class-instance, appointment-type or event scope. If a document is needed for those activities, attach it through the membership or session offering and design the join flow accordingly.

Versions and re-acceptance

Use Edit in place only for a typo or formatting correction that does not change what the person agreed to. Existing acceptances continue to point at the same version.

Use Publish as new version for any material change. The version number increases, the application rules remain attached to the document slug, and future flows can ask for acceptance of the new version. Previous evidence remains associated with the earlier version.

Archive a document when it should no longer be presented. Avoid deleting a document whose evidence must be retained: the current database relationship can cascade a waiver deletion into its acceptance rows.

What the evidence proves

An acceptance record can include the document and version, time, member or verified contact, IP address, user agent and acceptance method. This is useful consent evidence, but it is not a signature image, two-factor signing ceremony or immutable signed PDF. Decide with your own legal adviser whether the evidence and wording are suitable for the risk and jurisdiction.

Finally, test the exact public flow. Community-wide and signup requirements are handled by the profile/signup experience, while offering-linked rules are not enforced consistently by every quick checkout. For important terms, use the controlled wizard or permit flow and confirm an acceptance row exists.