Skip to content

Publishing Events

Events in Seva have a Published flag that controls whether they are visible through the API and registration components on your website. This lets you prepare event details before making them available to members.

StateVisible in admin?Visible on website?Registration open?
Draft (unpublished)YesNoNo
PublishedYesYesYes (within registration window)

When an event is unpublished, it returns a 404 to anyone trying to access it through the registration components. Members cannot see or register for draft events.

  1. Click Events in the sidebar and open the event you want to publish.
  2. Check the Published checkbox on the event detail page.
  3. Click Save.

The event is immediately available through the API. If your webmaster has already embedded the registration component with the event’s slug, members will be able to see and register for it right away.

You can also set the Published checkbox when creating a new event.

To take an event off your website:

  1. Open the event detail page.
  2. Uncheck the Published checkbox.
  3. Click Save.

The event disappears from your website immediately. Existing registrations are preserved — unpublishing does not cancel anyone’s registration.

These are two separate controls:

FlagPurpose
PublishedControls visibility on the website. Unpublished events are hidden.
ActiveControls whether the event accepts new registrations. Inactive events can still be visible but registration is disabled.

A typical workflow when an event is over:

  1. Leave it Published so attendees can still see event details.
  2. Set it to Inactive so no one can register.

To hide an event completely, uncheck both.

Even when an event is published, registration is only available within the registration window — the period between the Registration Begin and Registration End dates. Outside this window, the event is visible but the registration form is not available.

Before making an event public, verify:

  • Event name, description, and location are correct
  • Event dates are set
  • At least one active ticket exists
  • Ticket prices and pricing rules are configured
  • Registration window dates are set (if applicable)
  • Guest registration is enabled/disabled as intended