Skip to main content
The agenda is your event’s schedule: a list of sessions, each a titled slot on the event’s calendar — an opening keynote, a workshop, a networking break. Sessions are grouped by day and ordered purely by time: there is no manual sort order, so to move a session in the list you change its start time. Find it under Program & venue → Agenda in the event navigation.
The agenda anchors to your event’s start date. If the event doesn’t have one yet, the Agenda page asks you to set it first in Settings. Every session must fall on or after that date.

​
Add a session

1

Create it

Click Add session and give it a title. It lands on the event’s calendar; details and access are configured on its page.
2

Schedule it

Set Starts and, optionally, Ends — leave the end empty for an open-ended session. Times must be on or after the event’s start date.
3

Place it (optional)

Pick a Venue — one of the rooms or stages you defined under Venues. A session doesn’t need a venue to exist on the agenda.
4

Describe it

Add a description so attendees know what the session is about.

​
Who can see and join

Access to a session is controlled through perks, not through ticket types directly:
  • No perks selected — the session is open to everyone. This is the default.
  • Any perks selected — the session is restricted to attendees who hold at least one of them.
The full chain is ticket → perk → session: a ticket type (or add-on) grants a perk, and the perk carries the session with it. To make a session VIP-only, create a “VIP access” perk on the Perks page, bind it to your VIP ticket type, and select it on the session. A gated session never names ticket types directly — which means you can restructure your tickets without touching the agenda.
Sessions held in a perk-restricted venue inherit that venue’s restriction on top of their own. A session with no perks of its own, placed in a gated room, is still gated. See Venues.

​
Rules to know

  • The agenda’s order is time. There is deliberately no drag-to-reorder — change a session’s start time to move it.
  • Sessions need a start date to exist. An event without a start date has no agenda; set the date in Settings first.
  • Changing the event’s start date clears the whole agenda. Because every session is anchored to that date, moving it invalidates the schedule — the console asks for explicit confirmation before wiping it. Finalize your event dates before building a detailed agenda.
  • Sessions can be deleted. Unlike ticket types or venues, deleting a session removes it outright, and this cannot be undone. A confirm dialog stands in the way.
  • Sessions have no capacity or attendee list of their own. Access is a gate (perk holders may enter), not an enrollment — there is no per-session sign-up or headcount today.
  • Gating lives in perks, never in the description. Text in a session’s description doesn’t restrict anything; only its perk bindings do.
Speakers presenting in a gated session don’t need a special ticket: assigning them to the session from their speaker page automatically grants their registration the required perks.