Install a Calendar on a Team
Installing a calendar on a team adds a calendar at the team level — separate from any member's personal calendar — that you can use for a Team Event Type. Once installed, it can be the destination calendar where bookings are created, and, depending on the event type's conflict settings, a calendar Cal ID checks for conflicts.
This is useful when a team manages a shared, department, room, or resource calendar.
Important: Installing a calendar on a team does not automatically mean every Team Event Type uses it. You must select it in each relevant event type.
Only a team admin or owner can install and manage calendars at the team level.
- Go to Apps in Cal ID.
- Search for the calendar integration you want.
- Select it and click Install.
- Choose the account to install it on — depending on the integration, this may be your personal account or the team account.
- Complete the authorization and grant every permission the calendar provider requests.
- Once installed, the calendar is available for the team's event types.
Important: Select the correct account during installation and grant all permissions. Without them, Cal ID may not be able to access the calendar.
This is the key distinction for team calendars — keep the two concepts separate:
Concept | What it does |
|---|---|
Destination calendar | Where the Cal ID booking is created. |
Conflict calendar | The calendar(s) Cal ID checks to decide whether a slot is available. |
These can be different. A booking can be created on the Team Calendar while availability is determined from the hosts' calendars — it depends on the event type's conflict configuration. Do not assume the destination calendar is always the one used to check availability.
A Team Calendar is a scheduling/conflict calendar — it is not a team member. Installing it does not make it a host, organizer, or bookable person.
Installing is only the first step. To use the calendar, select it in the event type:
Team Event Type → Advanced → Add to calendar
This sets where bookings for that event are created.
Example. A team installs a Sales Team Calendar and selects it under Add to calendar for their 30-Minute Sales Consultation event. When a customer books 9:00–9:30 AM, the booking is created on the Sales Team Calendar — not only on the individual host's calendar.
The Check for conflicts setting decides which calendars Cal ID uses to see whether a slot is already taken. There are two options:
The configured Team Calendar is used as the conflict calendar for that event. If the Team Calendar has an event at a given time, that time can be blocked — even when the assigned hosts are personally free.
Example. The Sales Team Calendar has 3:00–3:30 PM → Internal Sales Meeting. Hosts Sarah, John, and Mike are all personally free at 3:00–3:30. Because the event checks the Team Calendar, 3:00–3:30 is not offered.
Cal ID checks the assigned organizers' calendars instead of the installed destination calendar. Whether a slot is offered depends on the organizers' availability and the event's scheduling type.
Example. At 10:00–10:30, Sarah is busy, John is free, Mike is busy. For a Round Robin event (one available host is enough), 10:00–10:30 can be offered because John is free — even if the destination calendar has an event then.
Setting | Behavior |
|---|---|
On | Cal ID considers the configured conflict calendar(s) when calculating availability, so existing events can block slots. |
Off | Existing events in the external calendar don't block availability through conflict checking — but existing Cal ID bookings are still protected, so the same slot is never double-booked. |
General rule: The calendar used for conflict checking depends on the Check for conflicts configuration — not on which calendar is set as the booking destination.
- A personal calendar belongs to one member. If it's used for conflict checking, that member's events make them unavailable during those times.
- A team calendar is installed at the team level. It can be the destination calendar and, when the event is configured to check it, a conflict calendar for the whole team.
Conflict behavior works together with the event's scheduling type:
- Round Robin distributes bookings among available hosts — one available host is enough to offer a slot (unless a Team Calendar conflict blocks it, when the event checks that calendar).
- Collective requires all assigned hosts to be free for the slot. If one required host is busy, the slot isn't offered.
- Fixed host requires that specific host to be free; their calendar and the applicable conflict rules determine availability.
Cal ID uses the normal availability logic for the assigned hosts — their configured availability, connected personal calendars, existing bookings, and event-type restrictions. For example, a Round Robin event with Sarah (busy), John (free), and Mike (busy) can still offer 2:00–2:30 PM because John is free; if all three are busy, the slot isn't offered.
Installing a Team Calendar alone does not determine availability — the event type's Check for conflicts configuration decides which calendar(s) are checked.
Updated on: 24/08/2026
Thank you!