What each method actually changes
| Method | What you get | Check before relying on it |
|---|---|---|
| Combined view | Several calendars visible in one app. | Which calendars your booking tool checks. |
| Sharing | Permission to view or edit a source calendar. | The recipient's permissions and your organization's policy. |
| ICS import | A snapshot of events at import time. | Later source changes won't refresh that snapshot. |
| ICS subscription | A feed that the receiving app refreshes. | Refresh delays and who can access the feed URL. |
| Managed sync | Event copies on a chosen destination, updated from their originals. | Privacy, direction, filters, permissions, and cleanup behavior. |
Try the option that fits the actual job
A household that wants to read one family calendar can often use sharing. Google lets an owner choose how much another person can see or change; a work or school administrator may restrict those choices. Use Google's calendar-sharing controls instead of publishing a private calendar publicly.
For a school or sports feed, an Outlook subscription can be appropriate. An imported file is a snapshot, while a subscription refreshes. Microsoft notes that subscription updates can sometimes take more than 24 hours. See Microsoft's import and subscription instructions.
Before buying a sync tool, check whether your scheduling service can already read every relevant calendar with the permissions you're comfortable granting.
Use copies when a destination needs its own busy time
Suppose Client A checks only your Client A calendar, but an appointment lives in a separate personal account. A private busy block can reserve that time on the client calendar without copying the appointment's name or notes.
In Sync My Cal, each rule has a source, destination, and copy mode. Two-way sync means originals flow in both directions. It doesn't mean you can edit either copy and have the change flow back. Edit the original event.
Managed copies are excluded as sources to prevent loops. If several client calendars need to know about the same original, give that original a direct rule to each destination.
Verify the result, not just the combined view
Open the destination calendar on its own. Confirm that the copy exists there, has the right busy status, and reveals only the fields you intended. Then move and delete the original to check updates and cleanup.
Busy blocks keep event details out of the copied event. They don't override a destination organization's access policies or erase information previously copied by another tool. Review existing events and sharing permissions when changing approaches.
Use the private-sync walkthrough for a field-by-field check, or the Google–Outlook guide for a first pair.