The signup form always collects a name, an email, a phone number, and notes. Anything else you need — a t-shirt size, a student's grade, a dietary restriction — is a custom form field. Answers travel with the signup and appear in the attendee and organizer emails and in the CSV export.
Add a field #
Open the event and choose the Form Fields tab.
- Add Field creates a new question.
- Add from Library inserts a question you have saved before, so common ones don't have to be rebuilt event after event.
- The arrows in the Order column move a question up or down the form.
- Save to Library puts a question into that reusable library. Edit and Delete change it on this event.
Deleting a field hides it from the form and from future CSV exports, but answers already collected stay stored.
- Label is the question as participants read it.
- Type decides the input: Text, Paragraph, Number, Date, Email, Phone, Dropdown, Multiple Choice, Checkbox, or Checkboxes (multiple).
- Options appears for Dropdown, Multiple Choice, and Checkboxes — put one choice on each line.
Key is generated from the label and locks once the field is created; it is the column name you'll see in the CSV export. Placeholder and Help text are optional hints, and Required stops the form from submitting until the question is answered.
What participants see #
Custom fields appear at the bottom of the signup form, after the standard fields, in the order you set.
- Name and email are always asked.
- Required fields are marked with an asterisk, and the form won't submit without them.
Below those, the event's own questions appear with their help text — in this example a required T-shirt size dropdown, a free-text student's grade, and a checkbox.
Reusing questions across events #
The field library is per-site, not per-event. Build a question once, click Save to Library, and on the next event use Add from Library to drop it in. Editing the copy on an event does not change the library entry, and vice versa — the library is a set of starting points, not a live link.
