Documentation Index

Fetch the complete documentation index at: https://docs.blackthorn.io/llms.txt

Use this file to discover all available pages before exploring further.

Min/Max Sessions

Prev Next
At a glance

Set how many sessions an attendee must and can choose. Put a floor and a ceiling on session selections per ticket type, add your own instructions, and block checkout until the minimum is met.

For: Organizers. Setup: Event Item (ticket) fields. Works with: Required Sessions and Session Rules.

Min/Max Sessions lets you control how many sessions an attendee selects when they register, per ticket type. Set a minimum so no one under-selects, a maximum so no one over-commits, or both.

A quick example

Your all-day conference includes 8 breakout sessions, and each Full Pass holder should attend between 3 and 5. On the Full Pass ticket, set Min Total Sessions to 3 and Max Total Sessions to 5. During registration, attendees can pick any 3 to 5 breakouts, and checkout will not complete until they have chosen at least 3.

What you can set

  • Minimum sessions: the fewest an attendee must select on that ticket. Leave blank (or 0) for no minimum.
  • Maximum sessions: the most they can select. Leave blank (or 0) for no maximum.
  • Instructional header: optional text shown above the session picker so attendees know what is expected (for example, "Choose 3 to 5 breakouts").

Checkout is blocked until the minimum is met.

:::(Success) (What attendees see)
The session picker shows your instructional header at the top. As attendees select sessions, they are kept within the min and max you set, and they cannot finish checkout until they have chosen enough.
:::

Set it up

  1. Open the Ticket (Event Item) you want to control.
  2. Set Min Total Sessions and/or Max Total Sessions.
  3. (Optional) Add Session Selection Header text to guide attendees.
  4. Save. The limits apply to that ticket's session selection at registration.

Which session feature should I use?

Feature What it does
Required Sessions Forces one specific session to be included with a ticket.
Min/Max Sessions Sets an overall floor and ceiling on session count per ticket.
Session Rules Groups sessions and enforces a min, a max, or a single choice within each group.

They stack: Min/Max sets the overall count, Session Rules control choices inside groups, and Required Sessions pre-add mandatory ones.

Before you publish

Make sure the ticket actually has enough related sessions to satisfy the minimum. If a ticket requires at least 3 sessions but only 2 are available, attendees will not be able to check out.

For Salesforce admins: fields
  • Event Item : Min Total Sessions (conference360__Min_Total_Sessions__c), Number, default blank. Minimum sessions an attendee must select during checkout. Blank or 0 means no minimum. Read/Edit: Events (Admin), (Organizer), (Community Platform User); Read Only: (Limited Access), (Lite User), (Read Only).
  • Event Item : Max Total Sessions (conference360__Max_Total_Sessions__c), Number, default blank. Maximum sessions an attendee can select during checkout. Blank or 0 means no maximum. Same permission sets as above.
  • Event Item : Session Selection Header (conference360__Session_Selection_Header__c), Text. Optional instructional text displayed above the session picker during checkout.

Related