> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ticketspotapp.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Set up conference registration and conference passes

> Create conference registration, offer full or daily passes, collect attendee details, and configure breakout-session add-ons in Ticket Spot.

Use **Conference** for a conference with attendance across several days. It starts with a **Conference Pass** and creates individual conference days. Breakout sessions and delegate questions are configured separately.

## Template starting point

| Setting | Initial choice |
| - | - |
| Schedule | Several days |
| Admission | Paid tickets |
| First offer | Conference Pass · suggested price 25 in your site’s currency |
| Capacity | 100 |
| Attendees choose a time | Not enabled |

These are editable suggestions, not recommended prices or venue limits. Replace the dates, price, and capacity with your own. See [how onboarding works](./overview#complete-onboarding).

## Choose the onboarding answers

Open **Create Event** in the selected workspace.

1. Select **Conference**, enter its name, and set the **Several days** range to the actual dates.
2. Choose a **Full event pass**, **Day passes only**, or **Full event pass + day passes** under **Paid tickets**. Check the generated day list.
3. Enter the starting price and capacity, then choose **Continue later** so you can review the delegate form, day-pass prices, and sessions in draft.

<Note>**Create my event** may publish immediately when the requirements are met. Use **Continue later** to finish setup as a draft. Review any plan or publishing message before sharing the event.</Note>

## Finish the event settings

| Where to go | What to configure |
| - | - |
| **Dates & Times** | Review the conference dates and set the operating hours for individual days. |
| **Tickets and individual dates** | Configure the full pass and [custom day tickets](/event-management/day-specific-tickets). Day tickets initially use the entered full-pass price and capacity. |
| **Additional Info** | Build a [conference registration form](/event-management/additional-information) with company, job title, and any relevant choices. Choose required and ticket-specific fields deliberately. |
| **Event Add-ons** | Create breakout sessions as saved events with tickets, then configure [add-on selection limits and time conflicts](/event-management/event-add-ons). |
| **Email Communication** | Send joining/arrival information and links to the program. Configure [multilingual communications](/branding-and-design/multilingual-communications) if needed. |

## A pass, a day, and a session are separate choices

A full conference pass describes admission across the event; a day pass is sold for a selected date. Neither automatically reserves a workshop seat. Use capacity-controlled add-on events for session reservations, rather than a preference question when places must be allocated. The [festival guide](./festival) explains shared versus custom day offers, and the [multi-day guide](./multi-day-event) covers onboarding restrictions for seated and timed-session events.

## Check the attendee experience

* Compare full-pass checkout with each selected day’s checkout and price.
* Register two delegates in one order and verify per-attendee form answers.
* Test breakout-session limits, conflicting selections, and the resulting confirmation.

Review the event’s saved status and [publish/share controls](/event-management/manage-events) when it is ready. Return to [all event types](./overview) to compare starting points.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.