> ## 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 festival tickets, full passes, and day passes

> Create a multi-day festival, choose full-event or day passes, customize daily prices and capacity, and verify festival ticket checkout.

Use **Festival** for an event with independently bookable or reportable days. Its several-day setup creates a date for each day and starts with a **Full Festival Pass**. You choose whether the days sell their own passes.

## Template starting point

| Setting | Initial choice |
| - | - |
| Schedule | Several days |
| Admission | Paid tickets |
| First offer | Full Festival 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 **Festival**, name it, and set **Several days** to the actual first and last dates. The suggested range spans three days and must be replaced if your festival differs.
2. Keep **Paid tickets** and choose **Full event pass**, **Day passes only**, or **Full event pass + day passes**. Review every day in the list.
3. Enter the starting pass price and capacity. Use **Continue later** to review daily prices in the editor before making them available.

<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** | Inspect every generated festival date. The initial day records cover calendar days; adjust operating times to match the program. |
| **Tickets** | Set the full-pass price and describe its admission scope when a full pass is offered. |
| **Individual dates** | Open each date and review its [custom tickets](/event-management/day-specific-tickets), price, quantity, and capacity. New day tickets initially copy the entered pass price and capacity. |
| **Event Add-ons** | Offer separately configured workshops or experiences through [add-on events](/event-management/event-add-ons). A date pass alone is not a workshop reservation. |
| **Check-in** | Choose scan limits and entry windows appropriate for full-pass and day-pass holders; verify the admission date and any re-entry policy. |

## Choose what each day sells

**Full event pass** keeps one pass on the festival. **Day passes only** creates tickets on the selected days without a full pass; a removed day has nothing on sale. **Full event pass + day passes** retains the full pass and lets selected days sell their own tickets; days without their own ticket use the shared pass. The “Recommended” badge does not select that option for you: Full event pass is the starting choice.

Separate day-pass choices in onboarding require a paid event spanning multiple days without assigned seating or attendee-selected session times. Follow the [multi-day guide](./multi-day-event) for the complete decision table. Check the total capacity with both full-pass and day-pass buyers; do not add the two inventories together as if they were separate venue space.

## Check the attendee experience

* Open the full-event page and each day separately; confirm the intended offers exist.
* Verify every day-pass price instead of assuming it is lower than the full pass.
* Check the ticket dates, shared capacity, and admission/re-entry rules for both kinds of pass.

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.