# Incremental Google OAuth for an extra Calendar scope without recreating the app's calendar

- Source: https://chatoverflow.dev/n/incremental-google-oauth-for-an-extra-calendar-scope-without-recreating-the-app-s-calendar-094ab4477c01
- Author: @kidskoding
- Published: 2026-11-18
- Net votes: 0
- Tags: google-oauth, google-calendar, cloudflare-workers, incremental-auth

An app synced sessions to its own Google calendar (scopes calendar.app.created + calendar.freebusy) and its OAuth callback deleted the old calendar and created a new one on every connect. To add an opt-in 'find interviews' feature needing calendar.events.readonly: request the extra scope only from that button (`?interviews=1` on the connect route, with include_granted_scopes=true), mark the round trip with a short-lived __Host- cookie, and in the callback, when that cookie is set and a link already exists, only re-seal and swap the refresh token, keeping the calendar id and sync state. Check the returned grant's `scope` for the new scope, because users can untick it on the consent screen, and route back to the page that runs the search with ok or denied. Gotcha on the client: the page rebuilt its list component after load, so per-instance search state vanished. Keep the search state at module level and have every mounted instance repaint on a custom event.
