Calendar Cross-Sync (Premium Feature 👑)
𝗖𝗮𝗹𝗲𝗻𝗱𝗮𝗿 𝗖𝗿𝗼𝘀𝘀-𝗦𝘆𝗻𝗰 — 𝗠𝗶𝗿𝗿𝗼𝗿 𝗲𝘃𝗲𝗻𝘁𝘀 𝗳𝗿𝗼𝗺 𝗺𝗲𝗺𝗯𝗲𝗿 𝗰𝗼𝗺𝗺𝘂𝗻𝗶𝘁𝗶𝗲𝘀 𝗶𝗻𝘁𝗼 𝗼𝗻𝗲 𝗼𝗳 𝘆𝗼𝘂𝗿 𝗮𝗱𝗺𝗶𝗻 𝗰𝗮𝗹𝗲𝗻𝗱𝗮𝗿𝘀 If you run a coaching community whose members also live in other communities you manage, keeping the calendars in sync is a copy-paste tax: every workshop, AMA or office hour announced in community A has to be re-created by hand in community B. Calendar Cross-Sync removes that work entirely. Pick the source communities you are a member of, pick one target community where you are admin or owner, hit save — every upcoming event in any of the sources is mirrored as a real Skool event in the target, complete with title, start and end time, description, meeting link, location and cover image. The configuration lives in the calendar panel footer next to the existing Subscribe button — a small cross-sync button opens a dropdown with two sections: source communities (multi-select, scoped to communities you have actually joined) and target community (single-select, scoped to communities where you are admin or owner). Hit Save and an immediate first sync runs; from that moment on, the cross-sync re-fires every time the calendar subscription save flow runs, so there is one trigger to remember instead of two. Updates to a source event patch the mirror in place — the mirror keeps its target event id, just the fields change. When a source event is deleted or expires, the matching mirror is deleted automatically; no manual cleanup, no stale entries piling up in your admin calendar over months. Recurring events are mirrored per occurrence, so each instance appears as its own row in the target calendar — the mirror map keys are stable across reloads and devices. The mirror map itself plus your source/target selection are part of Cloud Sync, so if you set up cross-sync on your laptop, the next time you open the calendar panel on a second device the same selection is already there and the same mirror map is used — no risk of accidentally creating duplicate mirror events from a different machine. All write traffic goes directly against the Skool API in the active tab using your own login cookies; the toolkit backend is not involved in any write path, so you cannot lose history by us going offline.