Skip to main content
Every event belongs to exactly one Business Unit. Creating one requires a name and a few timing details. Everything else is configured afterwards on the event’s own pages.

​
Create the event

1

Open the Business Unit

Switch to the Business Unit that will run the event, then go to Events.
2

Choose Create event

Give it a name (for example “Annual Partner Summit”). The event is created as a draft. Events stay private until published.
3

Set the schedule

Choose the start and end times and the event’s time zone. Times are always local to the event, in that time zone. The zone is stored explicitly rather than inferred.
An event can be created without a start time and filled in later. Publishing requires a start time.

​
Where it is presented

orriven does not host the event page — your own site does. Once the event has a page, record its address in the event’s Public page section: promotion short links redirect there, the hosted checkout returns buyers there, and offer share links are built from it. The checkout, order, and entry-pass pages behind it are orriven’s. See The event page and Hosted pages.

​
Event status

An event is always in one of three states: Publish and unpublish from the event’s Public page section. Draft is the default: ticket types, agenda, and forms can be built while the event stays unpublished.

​
The start date and the agenda

The agenda is scheduled relative to the event’s start date: a session’s day is “day 1”, “day 2” and so on from that anchor. Two consequences:
  • Agenda sessions cannot be added until the event has a start date.
  • Changing the start date clears the entire agenda. The console requires confirmation (Change date and clear agenda) before it applies. Changing the start date by one day would otherwise reschedule every session.
Settle the start date before building the agenda. If the date is not set, build ticket types, the registration form, and the event page first — none of those are anchored to the date.

​
Rules to know

  • One event, one Business Unit — ownership never changes.
  • Draft events are invisible to the public. There is no public preview link.
  • The event page is yours. Record its address so short links and checkout returns know where to go.
  • Publishing requires a start time; changing the start date later clears the agenda after an explicit confirmation.

​
Next steps

The event page

Publishing, the page address on your site, and the event’s languages.

Ticket types

Define how people register — capacity, waitlist, sale window.