Help center / Registration & ticketing
Create attendee types
Define the kinds of people coming — delegate, speaker, press, student — and what each one sees.
Attendee types are the single most structural decision in your setup. They drive which tickets someone can buy, which questions they are asked, and which badge they get.
Get these right before you build anything else.
Steps
- Open Form builder. Make sure the mode switcher at the top is on Registration form.
- Go to step 1 Attendee types.

Form builder on step 1 with the list of attendee types - Add a type and give it a name and a colour. The colour is how you will tell them apart at a glance in lists and on badges.
- Set the rest:- Price — the base price for this type.- Capacity — how many you will accept. Leave empty for no limit.- Description — shown to the registrant when they pick their type.- Requires approval — they register, then wait for you to approve. See Approve registrations.
- Save.
What each type controls
Which tickets they see. Every ticket is visible to specific attendee types — see Create a ticket type.
Which questions they answer. Any field can be restricted to certain types, so students get asked for a student ID and nobody else does. See Edit a question.
Which badge they get. Each type is assigned a badge template. See Assign badges to attendee types.
A sensible starting set
Most events need fewer types than people expect. Start with:
- Delegate — your paying attendee.
- Speaker — free, different badge.
- Press — free, usually with approval on.
- Staff — your own team and volunteers.
Add sponsors, students or VIPs only if they genuinely need different pricing, different questions or a different badge. If the only difference is a label, use a tag on the attendee instead.
Adding an attendee type after people have registered is fine. Deleting one is not — existing registrants are attached to it. Decide your set before you publish.
Common problems
Nobody can pick the type you just made. It needs at least one visible ticket. A type with no ticket is unreachable on the public form.
Everyone lands on the same type. One type is the default. If you only created one, every registrant gets it, which is correct for a simple event.
Capacity filled and people are still registering. Capacity applies per type. Check the ticket's own Quantity limit too — the two are separate.
You want different prices for the same type. Do not create a second type. Use price phases on the ticket — see Set up early-bird pricing.
more in registration & ticketing
- Add a question to your registration formPick a field type, label it, and place it on the right step.
- The 22 question typesWhat every field type is for, and which one to reach for when two look similar.
- Edit a question's label, options and validationChange the wording, build the option list, set validation rules, and restrict a question to certain steps or attendee types.
- Break your form into stepsSplit a long form across several screens, and decide where ticket selection sits.