Settings explained
How SYNCDATE works, what it copies and what it does not.
Last updated
This is the SYNCDATE documentation. Find answers about how syncing works, what it copies and what it leaves alone, and what each setting does.
Appearance: how copied events look
Every setting that decides what a copy looks like when it lands: title, availability, privacy, colour, guests and reminders.
Different settings per destination calendar
Set a shared default for a sync, then override it for one destination calendar. What you can vary, what you can't, and which way round it works.
Connect an AI assistant
What to have ready, what your assistant can reach, and how to fix or remove a connection.
Custom text and rules: decide what each copy shows
Write a copy's title, description or location yourself with pieces of the original dropped in, and use if-this-then-that rules for text, privacy, free or busy and colour.
Direction: one-way or two-way
Push copies one way and never touches the source. Mirror goes both ways. How to tell which one you need, and what changing it later deletes.
Filters: which events get copied
Which events enter a sync at all: the RSVP filter, working hours, Google's special event types, exclude rules and filter rules — plus what tightening one deletes.
What SYNCDATE can't do
The limits no plan removes: syncs don't chain, special event types are Google-only, feeds are read-only, and colour is approximate between providers.
Plans and limits
The five numbers that limit a setup, what each one means, and which one actually stops people.
Sync details: name, history, and how far ahead
The sync-wide settings: a sync's name, how much history it copies on its first run, and how far ahead it reaches.
SYNCDATE Team plan: seats, billing, admin access and leaving
How a SYNCDATE Team works: one bill, Pro limits per seat, inviting people, joining by company email domain, what the admin can and cannot see, and leaving.
Team sync rules: set what your Team's members can copy
How a Team owner limits what members' syncs copy: the team default, groups by email domain, exceptions, what each setting does, and how a change reaches existing copies.
What SYNCDATE decides on its own
The moments the product acts without asking: two calendars changing one event, an account that stops letting us in, a downgrade that removes copies, and a calendar that isn't yours to write to.