The OAuth connection method lets you control exactly which calendars Databook can see, using Google's standard login and approval flow. Use it if you want calendar-level control over what's shared, and the number of calendars you need to sync is comfortably under Google's practical limit (see below).
How it works
An integration account authenticates through Google OAuth and subscribes to the calendars it should sync. Access works the same way as sharing any Google calendar: a calendar owner grants the integration account read access, or the account is subscribed to calendars that have already been shared with it.
Because access is controlled entirely through normal Google Workspace calendar sharing and event-visibility settings, you don't need to maintain any separate exclude list of sensitive calendars or users on Databook's side.
What Databook can see
What's visible depends on whether a calendar belongs to the integration account or is only shared with it:
The integration account's own calendar: both public and private events sync.
Other calendars shared with read-only access: only events set to public visibility sync. Private events on these calendars appear as "Busy" with no further detail.
This means a calendar owner controls exposure event by event: leaving an event private keeps it out of Databook entirely, while marking it public lets it sync.
Setting it up
Create a Google Cloud project and enable the Google Calendar API.
Configure an OAuth consent screen and scopes, then create an OAuth client ID and secret. For calendar access, use the https://www.googleapis.com/auth/calendar scope, or the read-only variant if you don't need write access.
Share the client ID, secret, and scopes with your Databook account team.
Complete the OAuth login for the integration account and approve access, then share (or subscribe to) the calendars you want synced.
Before the integration can go live for all users, the Google app used for this connection needs to pass Google's verification process (logo, privacy policy, terms of service, and publishing). Development and testing can proceed with a limited set of test users while verification is pending.
Limits worth knowing
Limit | Detail |
Calendars per account | Google recommends staying under roughly 400 subscribed calendars on a single integration account. Beyond that, browsing and syncing performance degrades. |
Larger deployments | If you need to sync calendars for an entire organization, Workspace Delegation is the better fit. |
When to use OAuth
You want calendar-level and event-level control over what Databook can see.
Privacy sensitivity is high, and you'd rather private events never leave your environment.
The number of calendars to sync is comfortably within the roughly 400-calendar guideline.
Getting access
To set up the OAuth connection, contact your account team.