Set Up Ticketing on an Event

Ticketing starts from a normal SmartGig event. The event record holds the shared name, dates, venue, module access, team activity, and generated documents. The ticketing workspace then adds the customer-facing ticket page, ticket types, schedule choices, rules, promo codes, buyer questions, orders, attendees, gate check-in, refunds, disputes, finance reporting, and ticketing audit history.

The safest approach is to create the ticketing workspace while the event is still quiet, then work through the setup assistant before sharing any public link. A published ticket page can affect buyers immediately, so treat setup and launch as separate jobs.

Before you start

• Create the central event record first.
• Check that the Ticketing feature is included in your package.
• Make sure your role includes view and manage ticketing permissions for setup work.
• Connect Stripe in Settings > Payments if paid tickets will be sold online.
• Prepare the public event description, venue details, support email, buyer terms, refund policy, and any age or entry conditions.
• Decide whether this is a simple ticket sale or whether it needs sessions, invite-only access, promo codes, checkout questions, rules, passes, add-ons, scanner assignments, or detailed reporting.

Create the ticketing workspace

Use the setup assistant

The setup page has an Essential setup mode and an All areas mode. Essential setup keeps the route short for straightforward events. It focuses on event details, branding, ticket types, scanner readiness where needed, payment readiness, preview, and publish checks. Advanced areas stay out of the way until you choose them or until an existing setting makes them relevant.

• Simple path: use this for one public ticket sale with ordinary tickets, normal checkout, and no special restrictions.
• Schedule path: add this when buyers must choose a day, time slot, session, workshop, entry window, or reusable pass pattern.
• Entry plan: when Site Planner has a published snapshot, review the read-only entrances, queues, box office points, scanner locations, capacity, opening windows, scanner counts, and gate-flow warnings before briefing scanner teams.
• Public maps: when Site Planner has enabled public attendee or accessibility maps, the buyer page shows public-safe published maps without participant records, private notes, power details, or draft changes.
• Invite path: add this when the event should be private, invite-only, code-based, email-list based, or domain-restricted.
• Promo path: add this when discounts, partner codes, launch offers, capped allocations, or ticket-specific offers are needed.
• Question path: add this when you need buyer or ticket-holder information during checkout.
• Rules path: add this when checkout must prevent invalid baskets, such as clashing sessions or add-ons without an entry ticket.

Status and visibility

• Draft is for setup before public sales.
• Published makes the public ticket page available according to its visibility and access settings.
• Paused keeps the event visible where allowed but stops active sales.
• Closed ends sales and should be used when the event is no longer selling tickets.
• Archived removes the event from ordinary active work while preserving history.
• Public visibility makes the page broadly accessible.
• Private visibility requires the direct secure link.
• Invite-only visibility requires an accepted access code, invited email address, or allowed email domain.
• Hidden blocks public checkout and is useful while preparing or temporarily removing access.