Google Calendar - Access & permissions
Elevale uses OAuth 2.0 to read metrics from Google Calendar. Elevale does not modify data in the external system. Tokens and keys are encrypted server-side after validation.
Who can connect
Workspace admins and users with permission to manage Workspace Settings integrations.
Connections are managed from Workspace Settings → Integrations.
Requires [Business+] on your workspace plan.
What Elevale accesses
Read-only metrics exposed as KPI data points (see the Data points article).
Connection metadata (account IDs, property IDs, organisation tenants) needed for sync.
No write access to campaigns, repositories, accounting records, or CRM objects unless the provider API requires it for authentication only.
Google permissions
https://www.googleapis.com/auth/calendar see and change calendars on the Google account you sign in with.
https://www.googleapis.com/auth/calendar.events create and update events Elevale is allowed to write.
Sign in with the Google account whose calendar should block your Elevale week.
Sync direction
Into Elevale - busy time from the calendars you pick. That busy time blocks auto-schedule. Background refresh runs about every 15 minutes.
Out to Google - meetings you create in Elevale, including video join links and guests. RSVP responses come back onto the meeting.
Out to Google - scheduled work, on a separate calendar named Elevale Tasks, marked busy. You can turn this off.
Out to Google - approved leave, as busy time.
Branding
Google's consent screen says Elevale. It does not show a white-label app name, and branding settings cannot change it.
Disconnect and data retention
Disconnect from Workspace Settings → Integrations to revoke stored credentials and stop scheduled syncs.
Previously synced KPI history remains until you delete or convert those KPIs.
Subprocessors and data handling: Subprocessors and integrations
Google user data
How Google OAuth data is used and deleted: Google user data notice