Registration forms

The registration form is what attendees fill in when they sign up. Every event has one form, and it must have at least one field (including the required system fields) before the event can be published. Open Registration form in the event workspace to build it.

The builder has a canvas on the left showing your fields in order, and a palette on the right for adding new ones.

Default fields

Three system fields are always on the form and are collected on every registration:

Field	Type	Notes
First name	Text	Required, can't be removed.
Last name	Text	Required, can't be removed.
Email	Email	Required. The confirmation and e-ticket are sent to this address.

These are marked with a lock in the builder. You can't delete them, make them optional, or change their type — they're required for publishing. If they somehow go missing, BagEvent restores them automatically.

Adding fields

The palette groups fields into two sets.

Standard fields are ready-made common fields — click to add:

• Phone, Company, Job title, Country (dropdown), Address, VAT ID, and a Consent checkbox.
• Share with exhibitors and Attendee directory — ask these if your event has exhibitors or attendee networking. An attendee's tick is what lets stands see who visited them, and what lists them in the directory. See Exhibitors and booths and Attendee networking.

Custom fields let you build your own question in any of the supported types (see below). New custom fields start with a generated field key and a label you can rename.

Adding, removing, and reordering fields saves automatically. Reorder by dragging a field's handle. Deleting a custom field removes it and saves right away.

TIP

There's an AI helper on the form page too. Describe what you need to know about attendees, or upload a screenshot of an existing form, and it suggests extra fields for you to review before adding.

Field types

When you add a custom field or open a field's settings, you can choose from these types:

Type	Use it for
Text	Short single-line answers.
Textarea	Longer multi-line answers.
Dropdown	Pick one option from a list.
Radio	Pick one option, shown as buttons.
Checkbox	One or more choices, or a single yes/no tick.
Date	A calendar date.
Number	Numeric input.
File	Upload a document.
Image	Upload an image.
Phone	Phone number (international format).
Email	An email address, optionally verified by code.

Dropdown, Radio, and Checkbox fields take a list of options — enter one per line in the field's settings.

Field settings

Open a field's settings (the gear icon) to configure it:

• Field label — what attendees see.
• Field key — a stable, unique id used in answers and data exports. It's shown read-only and doesn't change when you rename the label.
• Help text — guidance shown beneath the field.
• Options — for dropdown, radio, and checkbox fields.
• Required — see below.
• Lock after registration — attendees can't edit this field once they've submitted.
• Organizer only — the field is hidden from attendees and used in the back office only.
• Verify email with code — for Email fields, requires attendees to confirm a one-time code sent to that address before submitting.
• Ticket visibility — show the field for all tickets, or only for selected ticket types.

Required fields

Mark a field Required to force attendees to answer it before they can complete registration. Toggle it from the required checkbox on the field row, or from the field's settings.

The system fields (First name, Last name, Email) are always required. Any custom field can be required or optional.

After editing a field's label, options, or required flag, click Save form to keep the change. Adding, removing, and reordering fields save on their own, but those in-place edits don't.

Per-attendee vs. per-order collection

By default the form is collected for every attendee in an order. You can change this under Registration → Rules with the Attendee information setting:

• Per attendee — the buyer and each participant fill in the form. Use this when you need details for everyone attending (badges, dietary needs, individual e-tickets).
• Buyer only — the form is collected once, from the person placing the order. Use this when one person registers on behalf of a group and you only need the buyer's details.

WARNING

Unique field values (below) are not enforced in buyer-only mode, because the form is only collected once per order rather than once per attendee.

Advanced form options

The builder toolbar also exposes:

• Unique field values — mark fields (like email or phone) that must be unique across registrations, to prevent duplicate sign-ups. Not enforced in buyer-only mode.
• Display rules — conditionally show fields based on the answer to a radio or dropdown question (for example, show "Company name" only when "Attending as" is "Business").
• Privacy — require attendees to acknowledge one or more privacy policies during registration, shown as a checklist or popup.
• Preview — see a live draft of the form as attendees will see it.

How the form relates to publishing

The form is one of the publish requirements for an event:

• The form needs at least one field, and it must contain the system fields First name, Last name, and Email.
• Because those three system fields are always present, a form is publish-ready as soon as it exists — but you'll usually want to add the fields you actually need first.

See Creating an event for the full publish checklist.

Next steps

• Tickets & inventory — the other half of what attendees complete when registering.
• Approvals — review submissions before confirming them.
• Data export — download form answers by field key.
• Multi-language events — translate form labels per language.
• Creating an event — where the form fits in the publish flow.