Connect Google Drive, Calendar, and Gmail changedclaude-tag/admins/connections/google
Nearest release: v2.1.240, published 3 hours before this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Recorded here
Lines+2added
Lines−14removed
From line
21
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits11to this page, all time
The whole hunk
from line 21, old and new numbered
/
from line 21
2121| **OAuth (Connect button)** | Fastest path. An admin signs in with a Google account that has access to the content Claude needs. |
2222| **GCP service-account key** | When you want a dedicated non-human identity in Google with auditable access, or need domain-wide delegation across your Workspace. |
2323
24Both routes create a credential and an allowed-websites rule path-scoped to that Google service (the Drive API path for Drive, the Calendar API path for Calendar, the Gmail API path for Gmail).
24Both routes create a credential and an allowed-websites rule for the Google hosts the connection uses.
2525
2626## Add the connection with OAuth
2727
2828<Warning>Use a dedicated Google account for this connection (for example, `[email protected]`), not your own. The connection is shared: anyone in a channel under the bundle's scope can ask Claude to read whatever this account can see in Drive, Calendar, and Gmail. A dedicated account starts with no access until you share the specific folders and calendars Claude needs, and keeps its activity under a separate identity in Google's audit log.</Warning>
2929
30In the bundle, click **Connect** next to **Google Drive**, **Google Calendar**, or **Google Gmail**. A scope checklist appears with read-only scopes selected by default. Each scope grants a specific permission:
31
32| Scope | What it lets Claude do |
33| :------------------------- | :--------------------------------------------------- |
34| `openid`, `userinfo.email` | Identify the connected account (selected by default) |
35| `calendar.readonly` | Read events and calendars |
36| `calendar.events.readonly` | Read events only (narrower than `calendar.readonly`) |
37| `calendar` | Create, edit, and delete events |
38| `drive.readonly` | Read files and folders |
39| `drive.file` | Create and edit files Claude itself created |
40| `gmail.readonly` | Read email |
41
42Check write scopes only if Claude should create or edit. Click **Sign in with Google Calendar** (or **Sign in with Google Drive**, or **Sign in with Google Gmail**), approve the Google consent screen, and the credential is saved.
30In the bundle, click **Connect** next to **Google Drive**, **Google Calendar**, or **Gmail**. The dialog lists the Google hosts the connection can reach; there are no scopes to choose. Click **Sign in with Google Drive** (or **Sign in with Google Calendar**, or **Sign in with Gmail**), approve the Google consent screen, and the credential is saved.
4331
4432The connection's reach is whatever the signed-in Google account can see. Share the relevant folders and calendars with that account in Google before testing.
4533
No line in this hunk matches that.