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

# Small events

> A lean setup for single-day events with one or two ticket types.

## Who this is for

You run a single-day event, such as a workshop, a party or a meetup, with one or two ticket types and a small team. You want to get set up quickly and not manage more than you need.

## What to set up

In priority order:

1. **Get your event created.** Creating an event is not self-service yet. Email [partners@plvr.io](mailto:partners@plvr.io) and the PLVR team sets it up. Your ticket types are arranged with the PLVR team too, so tell them what you want to sell.
2. **Finish your organization profile and add your team.** See [Onboarding](/getting-started/onboarding), [Organization settings](/organization/settings) and [Team](/organization/team).
3. **Complete your event page.** See [Event editor](/events/event-editor).
4. **Check your tickets.** Review price, quantity and status in [Ticket Management](/tickets/ticket-management). If you only sell one kind of ticket, see [General Admission in tiers](/tickets/scenario-ga-tiers) for staging prices (optional).
5. **Share your event page.** Use a [tracking link](/promotions/tracking-links) for each place you post it, so you can see what works.
6. **On the day, check people in.** Create login codes for your gate staff in [Onsite staff](/onsite/onsite-staff), and use the [Command Center](/onsite/command-center).

## What to skip

* Bundles, add-ons and multiple sessions, unless you truly need them.
* Affiliates and email campaigns, until you have an audience to reach.
* PLVR Tap, unless you want cashless payments.

## Team shape

Often one or two people cover everything. See the [roles overview](/roles/index), and the [Core team](/roles/core-team) and [Scanning team](/roles/scanning-team) pages.

## Common pitfalls

* Waiting until the last minute to ask the PLVR team for your event or ticket changes.
* Leaving gate staff without login codes before doors open.
* Free guests: issue [complimentary tickets](/tickets/scenario-comp-guests) rather than asking them to buy.


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