Registration form field types reference
This page lists the available field types for the registration form builder and the settings that control when a question shows.
To add fields to a registration form, see Build the registration form for an event.
Field types
Section titled “Field types”| Field type | What registrants see | When to use |
|---|---|---|
| Short text | A single-line text input. | Name, phone number, dietary note, or any brief open response. |
| Long text | A multi-line text area. | Longer open-ended answers, accessibility requirements, or notes. |
| Single choice | A set of options where only one can be selected. | Preferred session, T-shirt size, or meal selection with one answer expected. |
| Multiple choice | A set of options where any number can be selected. | Topics of interest, workshop preferences, or any question allowing multiple answers. |
| Checkbox | A single check box with a label. It can be required or optional. | “I agree to the photography policy” or a simple yes/no confirmation. |
| File upload | A file picker for the registrant to attach a document or image. | Photo ID, proof of certification, or completed forms. |
| Waiver | A waiver text with an acknowledgment checkbox; required by default. | Liability waivers, terms of participation, or any legally-binding acknowledgment. A required waiver must be checked to register; clear Required to make it optional. No document link can be attached. |
| Extra-charge | An optional paid add-on the registrant can choose to include. | Meal upgrades, equipment rental, or any optional paid item added at registration. |
Write-back policy
Section titled “Write-back policy”Choosing whether a question’s answers are written back to the registrant’s member profile isn’t available in the builder yet — the question editor has no write-back setting.
Conditional visibility
Section titled “Conditional visibility”Questions can be shown or hidden based on the answer to another question. The builder checks for circular dependencies when you set up conditions and shows an error if a loop is detected.
Conditions can compare an answer in different ways depending on the question type — for example, a choice question or a checkbox offers equals, does not equal, is any of and is none of; a multiple-choice question also offers contains; a text question also offers contains and starts with; and an extra-charge question also offers is greater than and is less than. Admin-only questions, file upload questions and waivers can’t be used in a condition.
If you change a question that other questions’ conditions depend on — its type, its choices, or who can see it — and the change means a condition no longer fits it, the builder warns you before saving. The affected questions, and any questions that depend on them, stop showing to registrants until you fix their conditions, and each is marked Condition needs fixing. If the question a condition depends on is left unanswered, only does not equal and is none of conditions show the question.
Conditions are carried over when you copy questions from another event. A copied condition points at the copied version of the question it depended on, or at the question already on this event if that one was skipped — as long as it can still be used in the condition. Otherwise the condition is removed and the confirmation counts it. A question that loses its condition always shows to the ticket types it is limited to, so the confirmation lists those questions.
Ticket-type scope
Section titled “Ticket-type scope”Each question can be limited to registrants who purchased a specific ticket type, using Ticket-type scope in the question editor. Registrants with other ticket types do not see the question. Leave it blank to show the question for all tickets.
Ticket scope is carried over by ticket-type name. When you copy questions, each restriction is matched to the ticket type on this event with exactly the same name. Restrictions with no match are removed. If a question loses all of them, it becomes visible to every ticket type — the confirmation lists those questions so you can set their ticket scope again.