Ticketing Setup Readiness and Publishing

Use the readiness checklist, preview, visibility settings, buyer policies, support details, and launch checks before opening public checkout.

Article guidance

Publishing is the point where setup becomes a buyer-facing workflow. SmartGig helps by showing a publish checklist on the ticketing setup page. Treat that checklist as the launch gate, not as a decorative status panel.

What the publish checklist checks

At least one active ticket type exists.
Paid ticket types have Stripe Connect readiness.
The event has date and venue context that buyers can understand.
Buyer terms are provided as text or a URL.
The refund policy is provided as text or a URL.
A support contact is available for buyer questions.
The public preview has been reviewed so the team knows what buyers will see.

Public page details

The event details area controls the buyer-facing name, description, dates, venue, policies, organiser details, support email, support phone, public FAQs, and optional portal information such as accessibility, travel, age limits, entry conditions, and venue map links.

Use plain public wording, not internal shorthand.
Put essential restrictions in the public page and terms, not only in an internal note.
Use the support email that customers should actually contact after purchase.
Add privacy, refund, and terms links where your organisation already maintains policy pages.

Visibility decisions

Use Draft while building: Draft events are internal and should not be promoted.
Preview before launch: Open the preview from the setup page and check tickets, policies, questions, schedule choices, and checkout wording.
Choose visibility: Use public, private, invite-only, or hidden based on how buyers should reach the page.
Publish only when ready: Resolve blockers, then publish. If something goes wrong later, pause or hide the event before making wider changes.

Invite-only setup

Access codes are useful when many people can use the same short code.
Multiple invite codes are useful when different groups need different codes.
Invited email addresses are useful for named guests or controlled allocations.
Email domains are useful for organisations, schools, sponsors, or internal staff groups.
Clear old invite settings when the audience changes so stale access does not remain active.