# Publish an event

Set up an event, its dated occurrences, ticket types, the two capacity caps, and the details checkout must collect.

## An event is a shell with dated occurrences

Create the event in **Event Ticketing** in Boni Panel, then add at least one occurrence and one ticket type. Nothing is bookable until the event is published.

| Field | What it controls |
|---|---|
| Name, description, media | What the public page shows |
| Venue and address | Where it happens, including map location where provided |
| Timezone | How start and end times are displayed; India Standard Time by default |
| Slug | The shareable public URL segment for the event |
| Status | Draft, published, archived or cancelled |

An occurrence is one dated instance with its own start, end and capacity. A recurring workshop is one event with several occurrences, which keeps the page, branding and reporting together.

## Ticket types

Each ticket type is priced and limited independently.

| Setting | Effect |
|---|---|
| Price | Zero makes the type free; any other amount routes the order through payment |
| Maximum per order | Caps how many of this type one booking may contain |
| Sales window | Opens and closes sales for this type without unpublishing the event |
| Per-occurrence capacity | Caps this type for a given occurrence |

## Two caps, deliberately

Occurrence capacity is a shared ceiling across every ticket type in that occurrence. Per-occurrence type capacity caps one type within it.

Set both when a venue has a hard headcount but you also want to limit a specific category. For example, a 50-seat occurrence can carry an unlimited-by-type student category and a 10-ticket guest category: the venue never oversells, and guests stay capped at 10.

Availability is enforced atomically at booking time, so two people booking the last seat at the same moment cannot both succeed.

## Checkout rules

An event can require details before a booking completes and limit the size of one order.

| Rule | Use it for |
|---|---|
| Require buyer phone | Registrations you will contact or verify |
| Require buyer email | Anything that must receive the confirmation and ticket links |
| Maximum tickets per order | One-registration-per-person events such as affiliation-gated entry |

Publish when the event, its occurrences and its ticket types are correct. The public page is then live at its slug and safe to share.

Next: [Booking and payments](/event-ticketing/booking-and-payments).

Canonical: https://docs.boni.one/event-ticketing/publish-an-event
Version: 1
Updated: 2026-08-19T04:55:39.539Z