Conflicting settings when using Group sessions

Group sessions can cause a settings conflict when used with booking in multiple calendars. This can happen in three scenarios that require booking in additional calendars and retrieval of busy time from the same calendars:

  • Team Booking page (Panel meetings): The page retrieves busy time from all member calendars and automatically adds the Calendar event to all member calendars when the booking is made.
  • Booking conditional on a single resource: The page retrieves busy time from the Owner’s calendar and the resource's calendar, and automatically adds the Calendar event to the Owner’s calendar and the resource's calendar.
  • Booking conditional on multiple resources: The page retrieves busy time from the Owner’s calendar and one of the resources’ calendars, and automatically adds the Calendar event to the Owner’s calendar and the assigned resource’s calendar.

In these three scenarios, it is impossible to use the Group sessions setting and vice versa:

  • You can create the above scenarios only for one-on-one sessions.
  • You can use Group sessions when you are not retrieving busy time from the same additional booking calendars.

So what should you do if you need to use Group sessions with the above scenarios?

  1. See if you can select to not retrieve busy time from the additional booking calendars.
  2. See if you can separate between Booking pages and Event types so that this limitation will not apply.

Group sessions and the number of bookings per day or per week

Group sessions cannot be used with the setting that limits the number of bookings per day or the number of bookings per week defined in the Time slot settings of the relevant Booking page or Event type. The limitation on the number of bookings per day or the number of bookings per week can cause slots to be partly filled and introduces a high level of complexity which can cause unnecessary confusion. 

Was this article helpful?
Thank you for your feedback!