Most people don’t have a calendar. They have a work Google account, a personal one, maybe an Outlook calendar from a client engagement — and meetings booked against any of them are equally real when someone asks if you’re free at two.
Read from everything, write to one
BunnyCal separates the two operations, because they want opposite defaults.
Conflict checking should be greedy. Every connected calendar you mark as a conflict source is queried when computing availability. A dentist appointment on your personal calendar blocks a work booking, and nobody outside sees why — the slot is simply gone.
Event creation should be precise. Exactly one calendar is the write target. When a booking is confirmed, that’s where the event lands, with the guest on the invite. Nothing gets written to the calendars you only read from.
Without it you get one of two bad outcomes: double-bookings, because the tool only looked at one calendar; or work meetings appearing on your family's shared calendar, because it wrote to all of them.
Connecting more than one account
You can connect several accounts from the same provider — two Google accounts is the common case — and each connection exposes its own calendar list. A typical setup:
| Calendar | Account | Conflicts | Writes here |
|---|---|---|---|
| Work — primary | you@company.com | ✅ | ✅ |
| Work — team events | you@company.com | ✅ | — |
| Personal | you@gmail.com | ✅ | — |
| Holidays in United Kingdom | you@gmail.com | — | — |
Read-only feeds like the holidays calendar are worth leaving unchecked: they’d otherwise blank out a fortnight of your availability in December.
Disconnecting cleanly
Each connection disconnects independently. Removing your personal Google account stops BunnyCal reading it immediately and revokes the token on Google’s side — it doesn’t touch the work account, and it doesn’t delete meetings already booked.
If you disconnect the account that holds your write target, BunnyCal asks you to pick a new one before any further bookings can be confirmed, rather than silently falling back to a calendar you didn’t choose.
See Connecting calendars for setup, and Troubleshooting sync if a calendar looks out of date.