Approving SYNCDATE for your workspace

For IT admins. Someone on your team wants to connect their work calendar and your org blocks third-party apps by default. Here is what SYNCDATE accesses and how to allow it.

SYNCDATE keeps a person's calendars in sync across accounts — for example their work calendar and a personal one — so a meeting on one shows up as busy on the other. It connects over standard OAuth using delegated permissions: it acts as the one user who signed in, only on their own calendars, and never reads anyone else's data in your tenant. There is no admin-wide access and no app installed for the whole organization.

What SYNCDATE requests
The full set of permissions, and nothing beyond it.

Microsoft 365 / Outlook

  • Calendars.ReadWrite — read and write the signed-in user's calendars
  • User.Read — read the user's basic profile (name, email)
  • offline_access, openid, email, profile — sign-in and token refresh

Google Workspace

  • calendar.readonly — read the user's calendars
  • calendar.events — create, update, and delete events on the user's calendars
Microsoft 365 (Entra ID)
Approve the app for the user who asked, or allow it tenant-wide.
  1. Sign in to the Microsoft Entra admin center as an admin.
  2. Go to Identity → Applications → Enterprise applications, then open Admin consent requests to find the pending request for SYNCDATE and approve it for the user.
  3. If you don't use the consent-request workflow, open Enterprise applications → Consent and permissions → User consent settings and allow user consent for the requested delegated calendar permissions.
  4. The user then returns to SYNCDATE and connects again — no further steps on your side.

SYNCDATE is a multi-tenant app registered against the common endpoint. Approving it grants delegated access only — it cannot read mailboxes or calendars other than the signed-in user's.

Google Workspace
Mark the SYNCDATE OAuth client as trusted for the calendar scopes.
  1. Sign in to the Google Admin console as a super admin.
  2. Go to Security → Access and data control → API controls, then Manage third-party app access.
  3. Choose Add app → OAuth App Name Or Client ID and search for SYNCDATE. If your policy needs the exact OAuth client ID, email vlad@syncdate.app and we'll send it.
  4. Set the app to Trusted so the calendar scopes (calendar.readonly and calendar.events) are allowed for your users.
  5. The user returns to SYNCDATE and connects again.
What SYNCDATE does not do
The boundaries, so you can approve with confidence.
  • It never reads or writes any calendar other than the accounts the user connects themselves.
  • It has no access to email, files, contacts, or other users' data.
  • Tokens are encrypted at rest, and the user can disconnect at any time, which revokes access immediately.
  • By default synced events show only as Busy — event titles and details are copied only if the user turns that on.
Questions?
Happy to walk through the security review with you.

Email vlad@syncdate.app or visit the support page.

Approving SYNCDATE for your workspace | SYNCDATE