The current calendar visibility in ChiliCal cannot be scoped by workspace or by user. Teams with specific privacy requirements (HR data, manager calendars set to private in Google Calendar, etc.) need to control who can see calendar details based on workspace membership.

Admins should be able to restrict calendar visibility on a per-user or per-workspace basis in ChiliCal, so that a user outside a given workspace cannot view or access calendar details belonging to users inside it, regardless of the account-wide Free/Busy setting.

Full calendar exposure across workspace boundaries doesn't meet the compliance and privacy requirements of all organizations. Booking and routing only require free/busy status, not full event detail, so scoped visibility controls would let teams protect sensitive calendars without giving up existing scheduling functionality.