Step 6 · Connect and choose scope

Last step. Now that credentials are saved, you pick which tools (Gmail / Calendar / Drive) to enable and run the OAuth flow. About 2 minutes.

Steps

1. Pick the tools you want

   The Google card’s Tools section has three rows — Gmail / Calendar / Drive. Each has a toggle: Off or Read-only.

   

   • Off: this tool isn’t connected. No OAuth scope requested.
   • Read-only: read access only. Requests gmail.readonly / calendar.readonly / drive.readonly as needed.

   You don’t have to enable all three. Just turn on what you want now. You can change this later by toggling and re-running Connect.

2. Click “Connect”

   Bottom-right of the card.

   

   The button moves through “Starting…” → “Waiting for consent…”, and a new browser tab opens.

3. Sign in to Google

   The new tab opens Google’s sign-in page. Use the same Google account you added as a test user in Step 3.

   

4. Pass the “Google hasn’t verified this app” warning

   Your OAuth app is in Testing mode, so Google shows a “Google hasn’t verified this app” warning. This is normal — you created the app, and you haven’t submitted it for Google’s verification process (which only matters for public apps).

   

   The bottom-right of the page has “Continue” (a blue text link) and “Back to safety” (a big blue button). Click Continue to proceed.

   Don't accidentally click 'Back to safety'

   “Back to safety” is the visually prominent button, but it aborts the OAuth flow. To proceed, click the understated text-link Continue on the left. If you misclick, just hit Connect again in the dashboard.

   Worried about the 'unsafe' warning?

   Google considers your OAuth client a “third-party app that hasn’t passed review” — hence the warning. In reality, you created the client, and no data leaves your device. Testing-mode apps always show this warning. It’s normal in this guide.

5. Review the requested scopes → Allow

   Google now shows the consent prompt: “Kura-chan wants to access your Google Account”, with the scopes broken out:

   • Gmail (Read): “See your email”
   • Calendar (Read): “See your calendars”
   • Drive (Read): “See your Google Drive files”

   

   • Verify the scopes match what you set to Read-only in Step 1
   • Scroll down and click Continue to grant

6. Confirm the success page and close the tab

   You’ll see a small success page — something like “You can now close this tab.”

7. Return to the dashboard tab

   Back in the dashboard tab, the Google card now shows your connected account instead of a Connect prompt.

   

Adding more scopes to the same account

Want to add Calendar later, even though you only enabled Gmail before?

1. In the Tools section, flip the new tool to Read-only
2. Click Connect again
3. Google asks you to consent to the additional scope. Click Continue

You’ll still have just one connection row, but with a higher scope count.

Connecting multiple accounts

Want to connect both a work and a personal Google account to the same realm?

1. With the first account already connected, click Connect again
2. Sign in with a different account on the Google page
3. After completion, you’ll see two Connection rows
4. Promote whichever one you prefer by clicking Set as default

Common gotchas

"Access blocked: Authorization Error"

Usual causes:

• You picked Web application in Step 4 — recreate as Desktop app
• You forgot to add yourself as a test user — go back to Step 3
• You signed into a different Google account — switch to the one you added as a test user

Stuck on "Waiting for consent…"

You probably closed or cancelled the OAuth tab. Click Connect again to restart with a fresh session.

Next

Connected? Confirm everything’s working in Verify the connection.