Draft means private
RecommendedSaving a draft does not publish the event. Continue editing the same event file instead of creating a duplicate.
This task-first Guide was reconciled against the production product on 14 August 2026. Use it to finish common organiser, attendee and event-day jobs. Open Docs when you need exact behaviour, integration rules or product boundaries.
Drafting can begin before every commercial check is complete. Paid publishing and money movement require stronger account readiness.
An event is the shared file for public details, tickets, audience work, operations, money and post-event records.
Saving a draft does not publish the event. Continue editing the same event file instead of creating a duplicate.
The public venue summary and the exact arrival record do not have to reveal the same amount of information.
Server-confirmed availability and current ticket state are authoritative. Old screenshots and stale browser pages are not.
Promotions, guest lists, broadcasts, automated messages and community tools solve different problems and have different permission boundaries.
Scanner access remains available on phones and tablets because admission cannot depend on a desktop workstation or perfect venue connectivity.
Analytics includes visual comparisons and event velocity so organisers can see pace and outcomes instead of reading a wall of numbers.
Several financial records can describe the same event without representing the same amount of money. EventOS keeps organiser-facing recipient allocation in one place: Payout splits.
The hosted EventOS experience is optional. Headless API access lets an organiser or product team keep its own website, app, design system and customer journey while EventOS handles event and ticketing infrastructure behind it.
Your brand can own the interface while EventOS remains the system of record for supported event, ticket, checkout, attendance and integration workflows. Keep sensitive credentials on your server and let EventOS enforce server-side rules.
The mobile web workspace is intentionally not a squeezed copy of every desktop tool.
Overview, Events, Create event, event basics, ticket types, Location and arrival, planning checklist, door staff, scanner, notifications, onboarding and normal account or security settings remain available.
Dense administration such as full sales management, bulk guest work, advanced messaging administration, community administration, Ticket Design, detailed Door Operations, settlement, payout splits, archive administration and API or webhook configuration can require desktop.
A single reference can open one ticket, while the signed-in attendee workspace keeps the wider event file together.
A suggestion is not proof that the person knows you. It is a discovery aid built from permitted relationship and event context. Shared attendance contributes only when the relevant attendee has made that attendance discoverable; blocking or tightening profile privacy removes those relationships from recommendation eligibility.
The fastest support report contains the event, role, device, approximate time and exact action that failed.
Record the event name, page address, account role, action attempted, approximate time, device and browser, visible error text and any relevant ticket or payment reference.