Group bookings and workshops

Group bookings

The specification allows a buyer or authorised contact to manage several places and obtain the relevant attendee details. The buyer is not automatically every attendee.

An order for several attendees has a person or a company as buyer. A company buyer can only be set by staff through the administration API, needs a company name and may have a VAT number. See buyer as a person or a company for the limits.

Before using the workflow on your release, verify how invitations, completion, changes and any transfer are implemented. The complete group journey was not verified through the interface here. Do not make an operating procedure depend on a button that has not been tested on your installation.

Workshops

Create a session with the explicit workshop-reservation attendance policy. A session type named “workshop” is insufficient by itself. Check the relevant occurrence/day, eligible ticket rights and capacity.

A favourite is not a reservation. A reservation for one occurrence does not automatically hold another. A switch must assess the old and new place as one coherent change.

The platform contains an internal check of deliverable workshop places. It does not refuse anything yet and has no screen or setting.

Acceptance test

Use two attendees to test the last available place, a repeated request and a switch. Inspect actual place counts after each result, not just a success message. Also test what someone without the required ticket can see.

Then check material access: a valid entitlement or confirmed reservation can be relevant. Read session material together with the current workshop rules.