Publishing an event makes the setup ready for buyers or invitees. Pausing and archiving are different actions: pausing is usually temporary, while archiving is for events that no longer need day-to-day attention.
Use event status deliberately, especially when orders, guests or campaigns already exist.
Publish when the basics are ready
Before publishing, check:
- Event name, date, time and venue.
- Ticket types and prices.
- Capacity and sales windows.
- Payment methods for paid events.
- Support and finance details at organisation level.
- Event page copy and branding.
- Terms, refund policy or buyer-facing notes where relevant.
Publishing too early can create buyer confusion. Publishing too late can slow down campaigns, guest invitations and partner communication.
Pause when sales need to stop temporarily
Pause or hide sales when you need time to correct a setup, investigate demand, handle a venue change or coordinate with partners.
If only one ticket type is affected, it is usually cleaner to manage that ticket type instead of pausing the whole event. For that workflow, read Hide, pause or sell out a ticket type.
Archive when the event is no longer active
Archiving keeps the active workspace cleaner after an event has passed or is no longer being managed. Do not archive an event just because ticket sales have ended if your team still needs easy access to guests, orders, reports or follow-up campaigns.
Before archiving, confirm that finance, support and reporting workflows are complete enough for your team.
Communicate changes clearly
Changing event visibility or sales status can affect buyers, partners and staff. If the event was already public, align status changes with clear communication so people understand what happened and what they should do next.