Skip to main content
A registration form is the set of questions a person answers when they register — company, dietary needs, T-shirt size. Forms are built once under Registration form in the event navigation, then attached to each ticket type that should ask them. Name and email are always collected; they identify the registration and are not part of any form.

​
Build and publish a form

1

Create a form

Choose Create form and name it (for example, “VIP questionnaire”). It starts as a draft.
2

Add questions

Use Add item to build the form. Question types include short answer, paragraph answer, single choice, multiple choice, and dropdown, plus layout items — section titles, text paragraphs, and media — that ask nothing.
3

Publish

A form has a draft version and a published version. Edits apply to the draft; attendees only ever see the published version. Publishing snapshots the draft into what the public sees — until then, edits change nothing on the event page.
4

Attach it to a ticket type

Open a ticket type’s page and pick the form in its Registration form section. That is where the binding lives — the forms page shows which types ask each form, but the choice is made from the ticket type’s side.

​
One form per ticket type

A ticket type carries at most one form — pick “None” and it asks only name and email. Several ticket types can share the same form, so a “General questionnaire” written once can be asked by every ticket. For a variation, Duplicate an existing form and edit the copy.

​
Reading the answers

  • Each attendee’s answers appear on their attendee detail page, under their registration.
  • The form’s Responses view lists everyone who answered, so submissions can be read form-by-form as well as person-by-person.

​
Rules to know

  • Attendees only see the published version. A draft edit — even to a form already in use — changes nothing until published again.
  • Forms never control access. A form collects information; it cannot gate who may register, hide a ticket, or hold a place. Use ticket type visibility and redemption codes for access.
  • Name and email are built in. They are always collected and cannot be removed; do not add them as questions.
  • An unpublished or archived form attached to a ticket type is flagged on the ticket’s page (“not published yet” / “archived”) before attendees reach an empty form.
  • Forms archive rather than delete — collected answers stay readable.
Keep forms short. Every required question reduces completions. Ask at registration only what is needed before the event, and collect the rest later.

Ticket types

Where a form is attached — one per type.

Attendees

Where each person’s answers are read.