Attestations

Attestations present legal or policy statements to attendees during registration: privacy policies, codes of conduct, data-sharing agreements, waivers. Mercleo records whether each attendee accepted or declined.

Where attestations come from

Attestations have two layers. Org defaults, managed at Settings → Attestations, apply to every event in your workspace automatically. Event-only attestations apply to a single event.

Open an event's Attestations tab, and (when your org has any defaults configured) you'll see a first table headed From org defaults, with a link out to manage them. Each default has a checkbox: unticking it opts this one event out of that specific default without touching any other event. A second table, Additional for this event only, holds attestations that exist just for this event. If your org has no defaults yet, the first table doesn't render at all, only the event-only one.

Creating an attestation

Open the event, go to the Attestations tab, and select New attestation in the page header. Each attestation has these fields:

• Title, required, maximum 200 characters. Shown as the checkbox label the attendee reads and checks.
• Description, optional, maximum 4,000 characters. Prose the attendee reads above the checkbox: the full policy text, or a plain-language summary.
• Document link, optional. Must be a full http:// or https:// URL. Renders as a “View document” link beside the checkbox so attendees can open the full document in a new tab.
• Required: on by default for a new attestation. Required attestations block the attendee from completing registration unless checked; optional ones can be left unchecked, and either way the choice is recorded.

New attestations are added to the end of the list; there's currently no manual reordering control on the tab.

Org defaults are created the same way, from Settings → Attestations, with the same four fields.

Required vs optional

A required attestation keeps the Continue button disabled on the Agreements step until the attendee checks the box. The server re-checks every required attestation on final submission too, so an unchecked required attestation rejects the registration even if the client-side check were bypassed.

An optional attestation can be left unchecked. Either way, the attendee's choice, accepted or declined, is recorded with the registration.

What the attendee sees

When an event has at least one applicable attestation (from org defaults, event-only, or both), an Agreements step appears in the registration wizard, between Additional Info (or Your Details) and Review.

On that step, each attestation shows its title, description, and, if you set one, a link to the document. Required attestations show a checkbox that must be checked to proceed; optional ones show a checkbox that can be left unchecked.

If an event has zero applicable attestations, the Agreements step is skipped entirely, and attendees move straight from Additional Info to Review.

Deleting attestations

Deleting an event-only attestation, or an org default, removes it from the Agreements step for future registrations. Registrations that already recorded a response for it keep that response; deletion doesn't touch history.