Q: Can booking types check only selected team calendars, instead of requiring all team calendars to be available?
I’m using the Agency Plan with multiple team members, each having their own integrated calendar.
My use case requires context-based availability, not collective availability:
• If a meeting is handled by Team Member A, only that person’s calendar should be checked
• If handled by Team Member B, only that calendar should be checked
• Multiple calendars should be checked only for intentionally created team meetings
Currently, it seems that all assigned team calendars always act as blocking calendars, so a time slot is bookable only if all calendars are available simultaneously.
Is it possible within a single Agency account to configure booking types so that only selected calendars are used for availability checks?
Or does independent availability per team member require separate TidyCal accounts?
Garry_AppSumoOriginals
Jan 19, 2026A: Thank you for your question about team calendar availability checking. I understand you're looking for context-based availability where only specific team members' calendars are checked depending on who's handling the meeting, rather than requiring all team calendars to be available simultaneously.
Here's how TidyCal's team booking currently works:
1. Collective meetings require all assigned team members to be available at the same time, so all calendars must be checked and show availability simultaneously.
2. Round Robin meetings require at least one team member to be available, but TidyCal still needs to check all assigned team members' calendars to determine who is available for assignment.
However, there is a solution for your use case: If you create team-based booking types where each booking type is hosted by just one specific member, only that member's calendar will be checked for availability.
To set this up, go to your booking type settings and assign only the specific team member who will host that particular booking type. This way, you can create different booking types for Team Member A, Team Member B, etc., and each will only check the relevant person's calendar.
This approach would give you the context-based availability you're looking for, though it does require creating separate booking types for different team members rather than having one booking type that intelligently selects which calendars to check.
Let me know if you have questions.