> ## Documentation Index
> Fetch the complete documentation index at: https://docs.orriven.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Ticket types
> Define how people register: capacity, sale windows, visibility, waitlists and approval — each as its own ticket type.
A ticket type is one way to register for your event — General admission, VIP, Speaker — each with its own capacity, sale window, visibility and rules. Enterprise events are often free, so think of a ticket type as a *registration option* rather than a paid product: today every ticket is free, and paid ticketing arrives later on the same types.
Find them under **Ticket types** in the event navigation.
## Create and publish a ticket type
Click **Create ticket type** and give it a name. It is created as a **draft** — invisible to the public and with no effect on your event — so you can configure it at your own pace.
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 yourself.
* **Registration form** — optional questions asked at checkout; see [Registration forms](/en/ticketing/registration-form).
* **Perks** — what this ticket includes; see [Perks](/en/ticketing/perks).
* **Sale window** — when sales open and close, in the event's local time. Leave empty to sell whenever the event page is live.
Click **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
| Status | What it means |
| ------------ | --------------------------------------------------------------------- |
| **Draft** | Invisible, no effect on the event. Configure freely. |
| **Open** | On sale (within its sale window and capacity). |
| **Closed** | Published but not selling. You can **Reopen** at any time. |
| **Archived** | Retired. Takes no registrations and disappears from lists by default. |
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 your event
* **Only Open or Closed types count.** While all your 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](/en/ticketing/offers).
## Approval
Turn on **Review each registration** and new registrations land as **Pending approval** instead of confirming automatically. You approve or reject each one from the attendee list.
While approval is on, **capacity becomes a soft limit** — you decide who gets in, not 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](/en/ticketing/offers).
* **Everything is free today.** Prices, and paid checkout, come later; a ticket type you create now will simply gain pricing when they do.
## Related
Ask questions when this ticket is chosen.
Codes that unlock hidden types and closed registration.
What a ticket includes — and what it unlocks in the agenda.
Every registration from the event page arrives as an order.