Creating sessions for your conference or event
Last updated August 5, 2026
Objective
This guide explains how to create sessions within a larger conference or event, including how to ensure sessions fall within the main event’s date range.
Key Steps
Step 1: Navigate to Events
Important thing to note: Events are created as templates first, and are marked as either a conference or session type on the event template.
Go to Engage → Events.
Click Add Event in the top right corner.
Select an event template (for example, Annual Conference).
Step 2: Create the Main Conference Event
Enter a name for your event (example: “March 3rd Annual Conference”).
Set the start date and time (for example, March 3rd at 12:00 PM).
Set the end date (for example, March 6th).
Complete additional event details as needed.
Click Publish to make the event live.
Step 3: Create a Session Event
Return to Events.
Click Add Event again.
Select the Session template.
Ensure the session dates fall within the main conference date range.
Step 4: Set the Session Date and Time
Choose the session date (for example, March 4th).
Set the start time (for example, 2:00 PM).
Set the end time (for example, 5:00 PM).
Enter a session name (for example, “Breakout Session”).
Click Publish.
Step 5: Repeat for Additional Sessions
Create as many sessions as needed.
Ensure each session falls within the conference’s start and end dates.
Publish each session individually.
Step 6: View Sessions in Event Mode
Navigate back to Events.
Open your main conference event.
Switch to step 7 Event Mode.
Click Previous if needed to view associated sessions.
Review all sessions listed under the main event.
Click any session to open and edit it.
Cautionary Notes
Sessions must fall within the main event’s date range to appear under the conference.
Each session must be published individually to be visible and available for registration.
Tips for Efficiency
Create and publish the main conference event before adding sessions.
Plan all session times in advance to avoid overlapping or scheduling errors.
Use consistent naming (e.g., “Breakout Session 1,” “Breakout Session 2”) for easy tracking.