Recipes

Multi-Session Conference

A multi-session conference lets attendees choose which sessions (breakouts, workshops, keynotes) to attend within a broader event. Forge models sessions as `conference360__Session__c` records that belong to the parent event, each with its own capacity, room, start time, and optional separate ticket linkage.

Sessions tab — add breakouts, assign rooms, and set per-session capacity limits.
Sessions tab — add breakouts, assign rooms, and set per-session capacity limits.

Before you start

  • Have your agenda drafted: session titles, start/end times, room or track assignments, and per-session capacity.
  • Decide if sessions are included with any ticket (open sessions) or restricted to specific ticket tiers (linked sessions). Linking sessions to tickets is the more advanced configuration.
  • If you are assigning sessions to speakers, have your speaker records created first (Speakers section in the left sidebar or the Speakers tab on the event).
  • Note: The *Planner Conference 2026* demo org models sessions as separate Event records for internal testing reasons. The standard and recommended model is Sessions (`conference360__Session__c`) as children of a single Event — that is what this recipe documents.

Steps

  1. Create your event (any location type) and navigate to the **Sessions** tab in the event workspace.
  2. Click **+ New Session**. Enter the **Session Name**, **Start Time**, and **End Time**. Assign a **Room** if relevant and set **Maximum Registrants** for the session capacity (independent of the event-level Maximum Attendees).
  3. Repeat for each session in your agenda. Group sessions by track or time slot — Forge displays sessions in chronological order on the agenda view.
  4. To assign a speaker to a session, open the session detail and use the **Speakers** related list to link one or more `conference360__Speaker__c` records.
  5. To restrict a session to a specific ticket tier, open the session and use the **Link Ticket** option. Only attendees who purchased the linked ticket can register for that session. Leave unlinked for sessions open to all ticket holders.
  6. On the **Page Designer** tab, verify the agenda block is enabled so the session schedule appears on the public registration page.
  7. Publish the event. On the registration page, attendees will see the full session agenda and can add sessions to their personal schedule.
Public agenda view showing session tracks, times, speakers, and room assignments.
Public agenda view showing session tracks, times, speakers, and room assignments.

Session waitlisting

When a session's Maximum Registrants count is reached, Forge automatically waitlists additional session registrations — independently of the event-level waitlist. An attendee can be confirmed at the event level but waitlisted for a specific session.

What this creates in Salesforce

Salesforce Field Mapping
ForgeSF ObjectSF Field
Sessionconference360__Session__cName
Parent event linkconference360__Session__cconference360__Event__c
Session start / endconference360__Session__cconference360__Session_Start__c / conference360__Session_End__c
Room assignmentconference360__Session__cconference360__Room__c
Session capacityconference360__Session__cconference360__Maximum_Registrants__c
Speaker on sessionconference360__Speaker__clinked via session speaker junction

Verify

  • All sessions appear in the Sessions tab with correct times, rooms, and capacities.
  • The public agenda view on the registration page shows the full session schedule.
  • Registering for a session past its Maximum Registrants limit results in a waitlisted session reservation.
  • Speakers are displayed on session cards if assigned.
  • Salesforce shows each `conference360__Session__c` linked to the parent `conference360__Event__c`.