Gmail one-time reconnect after the dedicated-OAuth cutover

If you connected Gmail to Turtini before April 29, 2026, you'll need to reconnect once. This is a planned, one-time event — it will not happen again on a regular cadence.

What changed (and why):
Gmail integrations use Google "restricted" scopes (gmail.readonly, gmail.send, gmail.settings.basic). Google requires those scopes to be CASA-verified at the OAuth-client level. Until the cutover, Turtini's Gmail integration shared the same OAuth client as the Firebase Auth (sign-in) flow — which meant a Gmail-scope verification audit would have touched your sign-in path too. That coupling is now broken: Gmail uses its own dedicated OAuth client, sign-in uses the Firebase one, and they can be audited independently.

What you'll see:
On your next Gmail-related action (read a synced thread, push your email signature, etc.), Turtini will surface a "Reconnect Gmail" prompt. The old refresh token is bound to the old OAuth client and Google won't accept it on the new one. It's not a bug, it's the cutover.

To reconnect:
1. Go to Settings → Integrations → Gmail
2. Click Reconnect Gmail
3. Complete the Google authorization flow — same scopes as before, just a fresh token bound to the dedicated client
4. Done — your inbox sync, signature push, and calendar pull resume immediately

Your old data is untouched. The threads + activity already synced to Turtini before the cutover stay exactly where they were.

If you also see "unverified app" in the Google flow, see the next article ("Why Google shows 'unverified app' when connecting Gmail"). That's a separate, parallel concern that resolves with CASA verification.