The problem:
Currently, event limit settings can only be set on an event-wide basis, and apply to all members of a round-robin event. But this is limiting because no buffer setting or interval setting etc. can ever serve all of the members of a big group. I speak from experience in saying that with 100+ members in our main round robin event, we have constant challenges trying to align the common (and changing) needs of everyone in the group.

The need:
Round robin members each have different needs for event limit settings (ie. buffers, minimum notice, time-slot intervals, booking frequency, limit future bookings, etc.)

The solution:
Team members should ideally be able to manage those settings for themselves in a round-robin event. With that in place, teams in round robins would see higher booking density, lighter support needs, fewer internal ops issues and have less friction in growing their teams in cal.com.