Set up calendar sync

Choose source, destination and direction

A sync connection relates selected calendars. A one-way connection copies the permitted representation from source to destination. A two-way connection requires a supported, writable calendar on each side. An ICS feed can be a source, never a writable destination.

Start with a dedicated pair of test calendars. Identify the original calendar for each event before deciding how you want information to flow. Avoid overlapping connections that copy the same source into the same destination without a clear reason.

Choose what travels

Select the permitted content level for the connection. Busy-only is appropriate when the destination only needs to know that a time is occupied. More detail requires both your choice and the workspace policy to allow it. Synchronizing a work calendar into a personal destination can be limited by organizational policy.

Verify one event lifecycle

1. Create one recognizable test event in the source, with no guests.
2. Wait for processing and confirm the expected representation in the destination.
3. Change its time at the source and check the copy.
4. Delete the test source event and verify the resulting behavior for that connection.

The processing path depends on provider notifications, polling, queues and provider availability. Do not assume an immediate update or a universal latency guarantee.

Verify an occurrence in a series

For Google/Microsoft connections, create a short weekly series, move one occurrence and cancel another. After processing, check the changed time and missing occurrence at the destination. A series across a daylight saving change should keep its local time. Make these changes at the source, not in the managed copy. See series and limits.

Operate an existing connection

Use pause/disable and the connection’s current status before changing a live setup. Stopping a connection and deleting copies are different operations; read the specific confirmation before proceeding. Do not manually edit a managed copy to test whether it is independent. See sync troubleshooting.

Manage syncs with Alvin

Open Alvin and ask: “Show my syncs.” The read-only canvas shows your permitted connections with source, destination, direction, status and selection rules. Two-way connections appear as one pair; details and editing links apply to each direction. The overview shows up to 100 pairs. Ask “Show my sync draft” to view your saved draft. Use its editing link to make changes in the sync editor.

For a new connection, try: “Sync my Work Test calendar one way to Private Test, busy-only and without all-day events.” In Ask before changes, Alvin first shows a preview. Check the source, destination, direction, content level and event selection before confirming. Two-way connections are also supported when your plan, calendars and policies allow them. You can continue setup in the editor from the preview; an existing saved draft is preserved.

For existing syncs, ask Alvin to change the selection rules for one direction, or pause and resume the pair. Changes follow your execution mode: Ask before changes requires confirmation; Execute automatically carries out permitted changes directly, including creating syncs. Pausing keeps existing copies. Changing selection rules can remove existing copies when their source events no longer match. Manage calendars, direction and content level of existing connections, and deletion, under Syncs.

Alvin needs sync read access for the view, sync write access for changes, and access to both calendars. If a connection is absent or access is denied, check its permissions under AI & Assistants. If the configuration has changed since the preview or the preview has expired, request a new one. A created sync continues independently of the chat, even after Alvin’s access is revoked; stop or remove it under Syncs.