Calendar setups, built for your situation
Find your situation. Every calendar problem is a slightly different one — here are the setups people arrive with, and the setup that solves each.
Most setups on this page are the same three parts: two calendars, a direction, and a rule that decides what is allowed to cross. The rule is a small function you can read before you run it, so “what will my colleagues actually see?” has an answer you can check rather than trust.
What differs between situations is the filter and the label. A household calendar wants the hours blocked and the contents kept back; a second employer wants the clash visible and the client unnamed. Both are the same mechanism pointed at different calendars.
Two pages sit outside that shape. The conference page has no rule and no second calendar of yours — just an API that puts a meeting into attendees’ calendars by invitation. The client booking link turns the rule around: rather than deciding what crosses to another calendar, it decides what counts as busy behind a link other people book.
What every setup here has in common
- Only what you allow crosses. Titles, descriptions, locations and attendee lists are cleared before an event is written to the other calendar, unless the rule says otherwise. Each page states this field by field.
- Nobody else has to install anything. Only you connect a calendar. Where an employer blocks third-party apps, the blocks can arrive as ordinary calendar invitations instead.
- One direction fits the free plan. Two calendar connections and one rule, syncing every 15 minutes and 14 days ahead. A two-way setup is a second rule, a booking page is free for one page reading one calendar, and a hosted calendar is Pro from the first call — which is where Pro starts.
Something else? Tell us the setup you need — rules are just small functions, so most situations are already possible.