Registration form field types reference
This page lists the available field types for the registration form builder and the write-back policies that control how answers interact with member profiles.
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. | “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 a required acknowledgment checkbox. | Liability waivers, terms of participation, or any legally-binding acknowledgment. The required checkbox cannot be turned off. |
| 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”The write-back policy controls whether question answers are saved to the registrant’s member profile.
| Policy | What happens to the answer |
|---|---|
| Fill empty only (default) | The answer is saved to the member profile only if that field is currently blank. If the member already has a value, the existing value is kept. |
| Overwrite | The answer always updates the member profile, replacing any existing value. |
| Registration only — no write-back | The answer is stored with the registration record only. The member profile is not changed. |
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 created by copying questions from another event are not copied — you must recreate them manually.
Ticket scope
Section titled “Ticket scope”Each question can be limited to registrants who purchased a specific ticket type. Registrants with other ticket types do not see the question. Leave ticket scope empty to show the question to all registrants.