Create and publish a ticket type
1
Create it
Choose Create ticket type and give it a name. It is created as a draft — invisible to the public and with no effect on the event.
2
Configure it on its page
Open the type’s detail page to set:
- Capacity — leave empty for unlimited. Only confirmed registrations count toward it.
- When full — stop taking registrations, or keep taking them as a waitlist.
- Visibility — public (shown on the event page) or hidden (redeemable by code only; see below).
- Approval — confirm automatically, or review each registration.
- Registration form — optional questions asked at checkout; see Registration forms.
- Perks — what this ticket includes; see Perks.
- Sale window — when sales open and close, in the event’s local time. Leave empty to sell whenever the event page is live.
3
Publish
Choose Publish. A confirm dialog shows the current configuration — including warnings such as “no capacity set” — before anything goes live. Once published, the type is Open and people can register.
Lifecycle: draft → open ⇄ closed → archived
Ticket types are never deleted — registrations, orders, and reports keep pointing at them. Archive instead. Restoring an archived type lands it on Closed, never Open, so nothing goes back on sale by accident.
How types change the event
- Only Open or Closed types count. While all types are drafts (or all archived), the event behaves as if no types exist: everyone registers under one default option.
- Once at least one type is Open, the event page offers a choice of tickets.
- If every published type is Closed, visitors see “registration is closed” — a deliberate state, useful between sale phases.
Hidden types (guest tickets)
Set visibility to Hidden — redeemable by code only for guest, VIP, or partner tickets. A hidden type never appears on the event page, and guessing its link gets the same answer as a ticket that does not exist. The only way in is a redemption code that points at it — see Offers & redemptions.Approval
Turn on Review each registration. New registrations land as Pending approval instead of confirming automatically. Approve or reject each one from the attendee list.While approval is on, capacity becomes a soft limit — admission is decided per registration, not by the counter — and the waitlist is disabled.
Rules to know
- Capacity counts confirmed registrations only. Pending, waitlisted, and cancelled registrations do not consume places.
- The public never sees numbers. A full ticket shows Sold out — a yes/no — never a remaining count.
- Waitlist: with “Keep taking them as a waitlist” on, registrations past capacity land as Waitlisted instead of being turned away.
- A draft is truly invisible. It does not appear anywhere public and does not switch the event into typed registration.
- Publishing always passes a confirm dialog — review the checklist it shows; it flags missing capacity and open-ended sale windows.
- Never deleted, only archived. Restoring lands on Closed, never Open.
- A redemption code can bypass “registration is closed” and hidden-type visibility — but never capacity or the sale window. See Offers & redemptions.
- Events are free to attend. Paid ticketing is not available yet; existing ticket types will continue to work when it is.
Related
Registration forms
Ask questions when this ticket is chosen.
Offers & redemptions
Codes that unlock hidden types and closed registration.
Perks
What a ticket includes — and what it unlocks in the agenda.
Orders
Every registration from the event page arrives as an order.