Calendar integration

Overview

Calendar integration lets Overshow read upcoming events you authorise from Google Calendar or Microsoft Outlook (Entra ID / Microsoft 365). When you connect either provider, Overshow obtains short-lived access tokens via the app.over.show token relay and fetches events directly from the provider API.

The feature is gated by the meeting detection feature flag. When enabled, it supports pre-meeting briefs (context drawn from your indexed captures shortly before events) and meeting enrichment (titles, times, and participants correlated with detected meetings).

What calendar integration provides

Capability	What you get
Event sync	Upcoming events from all calendars exposed for the connected account, not only the primary calendar.
Pre-meeting briefs	Short, capture-grounded context assembled in the five minutes before an event starts, using an on-device language model over relevant past material.
Meeting correlation	Overshow aligns detected meetings with calendar events by matching time windows so titles and attendees attach to the right session.
Source labelling	The source is tracked to distinguish Google and Microsoft events for traceability.
Desktop signals	The app notifies the UI when a fresh sync completes.
Settings surface	Settings → Calendar: connect or reconnect providers, view status badges, and manage consent through the provider flow.

Supported providers

Google Calendar

Desktop OAuth flows request the narrowest Google Calendar scope pair the current implementation needs: https://www.googleapis.com/auth/calendar.calendarlist.readonly to enumerate authorised calendars and https://www.googleapis.com/auth/calendar.events.readonly to read event metadata on each of them. Overshow does not request Google calendar write permissions for this integration.

Microsoft Outlook (Microsoft 365 / Entra ID)

Desktop flows request delegated Calendars.Read access for Outlook calendars backed by Microsoft 365 and Entra-joined tenants. Microsoft may also grant offline_access and standard identity permissions so the authorised connection can refresh without prompting you on every sync. Overshow does not request Microsoft calendar write permissions for this integration.

Provider comparison

Aspect	Google Calendar	Microsoft Outlook
Auth	Google OAuth	Microsoft identity
Token storage	Encrypted on device	Encrypted on device
All calendars	Yes, for authorised account	Yes, for authorised account
Polling	Periodic sync	Same cadence

Connecting a calendar

Settings → Calendar

Open Settings, then the Calendar tab. Choose Google or Microsoft and complete the OAuth sign-in in the system or embedded browser flow. Grant only the scopes presented; Overshow does not request calendar write permissions for this integration.

Token relay and refresh

The desktop app asks app.over.show for fresh provider access tokens. app.over.show stores encrypted provider tokens, refreshes them when needed, and returns short-lived access tokens to the desktop app. The desktop app then calls the Google Calendar API or Microsoft Graph directly to fetch authorised calendars and events; Overshow servers are not used as a proxy for the normal calendar event payload.

What data is synced

• Events across all calendars for the linked account (within the product’s configured horizons and privacy rules).
• Metadata used for correlation and briefs: calendar names, titles, start and end times, participant information, locations, and notes or descriptions where the provider exposes them.
• Source is recorded per event for consistency.

Conference links can also be extracted locally from event fields so meeting rows and briefing flows can link to the right call surface.

Calendar sync polls periodically while enabled, so new or moved meetings appear without manual refresh in normal use.

Pre-meeting briefs

Overshow watches for events starting soon. For each qualifying event, it generates a brief from relevant past captures. screen text, transcripts, and related indexed material. staying grounded in what you have already captured rather than generic advice.

What “relevant” means in practice

Relevance is driven by retrieval over your local index and the meeting’s context (time window, title, participants where available). If you have little history yet, briefs may be thin until capture volume grows.

How calendar enriches meetings

Overshow correlates detected meetings with calendar events by matching time windows. When a match exists, Overshow can attach:

• Event titles for clearer labelling in meeting views and history.
• Start and end times for alignment with transcripts and screen context.
• Participants where the provider lists them, improving search and brief targeting.

This enrichment sits alongside audio-based meeting detection; calendar data refines identity and metadata rather than replacing acoustic detection.

Revoking access and reconnecting

Current desktop builds expose connect and reconnect actions plus provider status badges. To stop future cloud access immediately, revoke Overshow in your Google account, Microsoft account, or organisation admin controls. After revocation or token expiry, the next refresh attempt fails and cloud sync stops until you reconnect.

Calendar reconnect must use Google or Microsoft OAuth. Email magic links can sign you in to Overshow, but they cannot grant calendar provider scopes, so they do not create a calendar connection.

Privacy and security

Topic	Handling
Tokens	Stored encrypted on the device and, for cloud refresh, encrypted at rest on app.over.show.
Consent	OAuth and in-product messaging make cloud sync an explicit choice.
Data minimisation	Read-only calendar scopes; no write path for events through this integration.
Revocation	Provider-side revocation or expired consent ends authorised access until you reconnect.

When calendar integration helps most

Calendar integration is strongest when your work calendar is the same system you connect, when meeting detection is enabled, and when you already have indexed captures for briefs to draw on. Teams with strict compliance should align connection with information governance: read-only access still implies metadata leaves the provider under the terms of your OAuth grant.

Workers and desktop events

Two concerns run on different schedules so the product stays responsive:

Component	Role	Cadence / trigger
Calendar sync	Pulls fresh events from Google or Microsoft via authorised tokens	Periodic polling
Pre-meeting brief	Builds briefs when an event is imminent	Events starting soon
Meeting correlation	Correlates detected meetings to calendar events	Driven by new detections and synced events

When cloud sync completes a successful cycle, the desktop app refreshes calendars, badges, and brief readiness automatically.

Offline and token edge cases

If the device is offline, polling continues to schedule but fetches fail until connectivity returns. Automatic token refresh means transient expiry is usually invisible; persistent failure (revoked token, password change policy) surfaces in Settings and may require reconnecting the provider.

Scopes at a glance

Provider	Scopes / permission	Purpose
Google	https://www.googleapis.com/auth/calendar.calendarlist.readonly + https://www.googleapis.com/auth/calendar.events.readonly	Enumerate calendars and read event metadata
Microsoft	Calendars.Read (delegated) and, where granted by Microsoft, offline_access for refresh continuity	Read calendars and events for the signed-in identity

Administrators may gate these scopes behind organisation consent workflows; if consent is pending, the connect button may succeed only after an admin approves the enterprise application.

Tips

• Connect the account where recurring client and internal meetings are scheduled so correlation and briefs match reality.
• Keep capture running in the apps you care about; briefs and enrichment both improve with richer local history.
• After timezone or daylight-saving changes, allow one or two sync cycles before judging missing events.
• If you use multiple calendars under one account, you do not need to pick only “primary”. Sync includes all authorised calendars.
• For shared machines, sign out and, if policy requires it, revoke provider access when you finish a session.
• If briefs feel generic, widen capture in the apps where that work actually happened; briefs cannot cite material that was never indexed.
• Treat participant lists as hints only; providers differ in how they expose attendees on recurring series and forwarded invites.