> ## Documentation Index
> Fetch the complete documentation index at: https://cal.id/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# Install a Calendar on a Team
> Install a shared calendar at the team level in Cal ID and use it as the destination or conflict calendar for team event types, plus how conflict detection interacts with host calendars.
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.
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.
## Who can install a team calendar
Only a **team admin or owner** can install and manage calendars at the team level.
## Install a calendar on a team
Go to **Apps** in Cal ID.
Search for the calendar integration you want and click **Install**.
Select 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.
Select the correct account during installation and grant all permissions. Without them, Cal ID may not be able to access the calendar.
## Destination calendar vs conflict 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. A team calendar is a scheduling and conflict calendar; it is **not** a team member, host, or bookable person.
## Configure the calendar in your event type
Installing is only the first step. To use the calendar, select it in the event type under **Team event type → Advanced → Add to calendar**. This sets where bookings for that event are created.
For example, a team installs a **Sales Team Calendar** and selects it 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.
## Conflict detection
The **Check for conflicts** setting decides which calendars Cal ID uses to see whether a slot is already taken.
The configured team calendar is used as the conflict calendar for that event. If it 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*. Sarah, John, and Mike are all personally free at 3:00–3:30, but 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, and 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.
### Conflict detection on vs off
| 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. |
The calendar used for conflict checking depends on the **Check for conflicts** configuration — not on which calendar is set as the booking destination.
## Team calendar vs personal calendar
* 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.
## How scheduling types interact
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.
* **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.
## If the team doesn't install a team calendar
Cal ID uses the normal availability logic for the assigned hosts — their configured availability, connected personal calendars, existing bookings, and event-type restrictions. Installing a team calendar alone does not determine availability; the event type's **Check for conflicts** configuration decides which calendar(s) are checked.
## Related team calendar setup
Distribute team bookings automatically among available hosts.
Book meetings that need several hosts present at once.
Set the calendar permissions Cal ID needs for conflict checking.
Choose where an event type's bookings are created.
## Related topics
- [Teams in Cal ID](/docs/teams/overview.md)
- [Round-Robin Scheduling](/docs/teams/round-robin.md)
- [Collective Events](/docs/teams/collective.md)
- [Connect Google Calendar](/docs/apps/google-calendar.md)
- [Add Events to Calendar](/docs/event-types/advanced/add-to-calendar.md)