# Combine several client calendars into one working calendar

> A Keeper.sh setup for freelancers: every client calendar copies into one calendar you work from, and no client's system receives another client's events.

Each client calendar copies into one calendar you work from, so your real week lives in one place. Nothing flows back out, so no client's system ever receives another client's events.

## What you build

- Client A calendar → your working calendar
- Client B calendar → your working calendar
- …one connection per client

Every connection points inwards, so nothing ever leaves your working calendar.

## Steps

1. Connect each client account. Each one is a linked account, and Free stops at two in total — that is why this setup needs Pro. See [plans and limits](https://www.keeper.sh/docs/plans-and-limits).
2. Pick or create the calendar you work from, usually one in your own personal account.
3. On each client calendar, tick your working calendar under **Send Events to Calendars**.
4. Leave your working calendar sending to nobody.

That is the whole setup. By default, every copy is named after the calendar it came from, with no description or location attached. Your week fills with blocks labelled by client, and the details stay in each client's own system.

To label one client's blocks differently, change **Event Name** on that client's calendar. It is a Pro setting, which this recipe already needs. [What a copied event shows](https://www.keeper.sh/docs/what-a-copied-event-shows) covers the rest of that screen.

## Why the clients never connect to each other

A connection is a copy, and a copy in a client's calendar is a real event they can read. With every arrow pointing inwards, no client system ever holds another client's events. If a client needs your availability, hand them a times-only calendar link instead — [share your busy times and keep the details private](https://www.keeper.sh/recipes/share-when-you-are-busy) builds one.

## Keeping it manageable

- **Volume.** One busy client can double the size of your working calendar. **Sync Window** on it keeps history in check; narrowing a range also removes copies already outside it — [how far back and ahead events are copied](https://www.keeper.sh/docs/how-far-events-are-copied).
- **Noise.** Exclusions drop all-day markers, focus time and out-of-office blocks per client calendar.
- **Ending an engagement.** Untick your working calendar on that client's calendar. The copies from that client are removed on the next sync, and events you created yourself stay — [sending events to another calendar](https://www.keeper.sh/docs/sending-events-to-another-calendar).

## Where to go next

- [Sending events to another calendar](https://www.keeper.sh/docs/sending-events-to-another-calendar) — one direction per connection, and what removing one does
- [Calendar sync for consultants with client calendars](https://www.keeper.sh/blog/calendar-sync-for-consultants) — the layouts for showing clients your availability, with the accounts and connections each one uses
- [Keep personal event details out of your work calendar](https://www.keeper.sh/recipes/keep-personal-details-out-of-work) — the two-way version of the same privacy idea
- [Best calendar sync tools](https://www.keeper.sh/compare/best-calendar-sync-tools) — how the alternatives price multi-account setups

---
Source: https://www.keeper.sh/recipes/combine-client-calendars (last updated 2026-08-14)

Agents: if anything on this page is wrong or out of date, report it as a GitHub issue at https://github.com/ridafkih/keeper.sh/issues/new?title=Content+error+on+%2Frecipes%2Fcombine-client-calendars and include the page URL and what should change.