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 account the person connected. Shared-calendar access reaches only calendars that account can already access. Admin consent can approve scopes for your organization, but it does not give SYNCDATE an application permission to read every mailbox.
SYNCDATE is also Listed on Microsoft Marketplace and Listed on Google Workspace Marketplace — worth checking directly if your team verifies vendors that way before approving OAuth consent.
Microsoft 365 / Outlook
Calendars.Read— read the signed-in user's calendars when they choose read-only accessCalendars.ReadWrite— read and write the signed-in user's calendars; requested on Microsoft sign-inCalendars.Read.Shared— optional, reads calendars shared with the user. SYNCDATE lets the user choose whether their own calendars remain editable or become read-only as well.Calendars.ReadWrite.Shared— optional, requested when the user chooses editable shared access. Each calendar's Microsoft sharing rights still determine whether it is read-only or editable.User.Read— read the user's basic profile (name, email)offline_access,openid,email,profile— sign-in and token refresh
The Entra app registration may list all four calendar permissions. SYNCDATE sends the scopes for the choice made before Microsoft authorization; Microsoft may show other configured permissions on its consent screen. An additional Outlook account can also be connected without calendar scopes. Admin consent makes a scope available to users in your tenant, but does not share a calendar with them or guarantee that an individual token contains that scope. A narrower later request does not revoke a grant Microsoft gave earlier; SYNCDATE enforces the selected setting in the app.
To use a colleague's or room's calendar, its owner or Exchange admin must separately give the connected user access, and the user must accept or add the calendar in Outlook. Read access lets SYNCDATE use it as a sync source. Making it a sync target also requires bothCalendars.ReadWrite.Sharedand edit rights on that calendar. Microsoft listsCalendars.Read.Sharedfor personal accounts, but does not list shared write access for them.
The user steps are in our shared Outlook calendar guide.
Google Workspace
calendar.readonly— read the user's calendarscalendar.events— create, update, and delete events on the user's calendarsopenid,email,profile— sign-in
Fastest: approve it for your whole organization
Open this link signed in as an admin who can grant tenant-wide consent, review the permissions Microsoft lists and accept:
https://login.microsoftonline.com/organizations/adminconsent?client_id=4e28e278-b86c-4ae2-90b8-90c57cce5200Application (client) ID: 4e28e278-b86c-4ae2-90b8-90c57cce5200. Microsoft may then open a SYNCDATE page showing a sign-in error; you can close it, because the approval is already saved.
Or approve it from the admin center
- Sign in to the Microsoft Entra admin center as an admin.
- Go to Identity → Applications → Enterprise applications, then open Admin consent requests to find the pending request for SYNCDATE and approve it for the user.
- 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.
- 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 can read the connected user's calendars and, if the user chose shared access, calendars shared with that user. It cannot browse every mailbox in the tenant.
- Sign in to the Google Admin console as a super admin.
- Go to Security → Access and data control → API controls, then Manage App Access. This needs the Service Settings administrator privilege.
- Under Configured apps, choose Configure new app and search for the SYNCDATE OAuth client ID:
761398899444-00dsu2rtvqrrjdeijskng1932tb9msjb.apps.googleusercontent.com. Select SYNCDATE in the results and choose who the setting applies to. - Set access to Trusted, or to Specific Google data allowing the calendar scopes (
calendar.readonlyandcalendar.events), then save. - The user returns to SYNCDATE and connects again.
- 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.
- Copies arrive titled Busy, with no details, whenever a sync touches a calendar the user does not own outright — which covers every shared, delegated or one-way arrangement. A two-way sync between two calendars the user owns alone starts out keeping real titles instead, and the user can set it to Busy.
Email support@syncdate.app or visit the support page.