Connect Google Drive, Calendar, and Gmail changedclaude-tag/admins/connections/google
Nearest release: v2.1.290, published under an hour before upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Upstream edited this page at 5 Oct 2026 18:53 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 5 Oct 2026 19:07 UTC.
Upstream edited
Recorded here
Lines+20added
Lines−18removed
From line
6
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits11to this page, all time
## Add the connector with Google sign-in ## Add the connector with a service account ## Add the connection with OAuth ## Add the connection with a service account
The whole hunk
from line 6, old and new numbered
/
from line 6
66
77<BetaNote />
88
9<Note>Connections are added inside an [Access bundle](/docs/claude-tag/admins/add-connections#your-first-access-bundle). At [`claude.ai/admin-settings/claude-tag`](https://claude.ai/admin-settings/claude-tag), open **Access bundles** in the left navigation, click into a bundle (or **Create** one), and go to its **Credentials** tab.</Note>
9Connecting Google Drive, Calendar, and Gmail lets Claude read documents, spreadsheets, calendar events, and email in any channel where the connector is on. Claude connects with its own credential, not a person's.
1010
11Connecting Google Drive, Calendar, and Gmail lets Claude read documents, spreadsheets, calendar events, and email from any channel under the bundle's scope. You add it as a connection inside an [Access bundle](/docs/claude-tag/admins/add-connections); the credential belongs to the agent, not to any person.
11This connector calls Google's HTTP APIs, and it's separate from members' personal claude.ai connectors. A member's own Google connector applies in one-to-one DMs. Claude can also [use it in a channel](/docs/claude-tag/concepts/personal-connectors) for that member's own tasks, after the member allows it.
1212
13This is an HTTP API connection, not a personal claude.ai connector. A member's own Google connector applies in one-to-one DMs. Claude can also [use it in a channel](/docs/claude-tag/concepts/personal-connectors) for that member's own tasks, after the member allows it.
14
1513## Choose OAuth or a service account
1614
17The connection picker offers two routes:
15The **Add a connector** dialog offers two routes to Google:
1816
1917| Route | When to use |
2018| :- | :- |
21| **OAuth (Connect button)** | Fastest path. An admin signs in with a Google account that has access to the content Claude needs. |
22| **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. |
19| **Google sign-in** (the **Google Drive**, **Google Calendar**, or **Gmail** entry) | Fastest path. An admin signs in with a Google account that has access to the content Claude needs. |
20| **GCP service-account key** (the **Custom connector** entry) | When you want a dedicated non-human identity in Google with auditable access, or need domain-wide delegation across your Workspace. |
2321
24Both routes create a credential and an allowed-websites rule for the Google hosts the connection uses.
22Both routes create a credential and an allowed-websites rule for the Google hosts the connector uses.
2523
26## Add the connection with OAuth
24## Add the connector with Google sign-in
2725
28<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>
26<Warning>Use a dedicated Google account for this connector (for example, `[email protected]`), not your own. The connector is shared: anyone in a channel where it's on 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>
2927
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.
28Go to [**Organization settings > Claude Tag > Connectors**](https://claude.ai/admin-settings/claude-tag?access=connectors), click **Add**, and select **Google Drive**, **Google Calendar**, or **Gmail**. The connect form lists the Google hosts the connector can reach; there are no scopes to choose. The first credential you add for a service from the **Connectors** tab is on in every workspace and channel as soon as you save it. To give it narrower reach, see [where a new connector applies](/docs/claude-tag/admins/add-connections#add-a-connection) before you sign in. 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.
3129
32The 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.
30The connector's reach is whatever the signed-in Google account can see. Share the relevant folders and calendars with that account in Google before testing.
3331
34## Add the connection with a service account
32## Add the connector with a service account
3533
36In the bundle, click **Connect** next to **Custom tool** and choose **GCP access token (with Service Account Key)**.
34Go to [**Organization settings > Claude Tag > Connectors**](https://claude.ai/admin-settings/claude-tag?access=connectors), click **Add**, and select **Custom connector**. Fill in these fields in the connect form.
3735
3836| Field | Value |
3937| :- | :- |
38| Name | A name for the connector, such as `Google Workspace` |
39| Credential type | **GCP access token (with Service Account Key)** |
4040| GCP service account key (JSON) | The JSON key file from Google Cloud Console |
41| Scopes (optional) | The Google API scopes to request (for example `https://www.googleapis.com/auth/drive.readonly`). If you leave the field empty, the connection requests `https://www.googleapis.com/auth/cloud-platform`. |
41| Scopes (optional) | The Google API scopes to request (for example `https://www.googleapis.com/auth/drive.readonly`). If you leave the field empty, the connector requests `https://www.googleapis.com/auth/cloud-platform`. |
4242| Subject (optional) | A user email to impersonate via domain-wide delegation. Set this for Workspace data (Drive, Calendar, Gmail, Docs). |
4343| Allowed websites | `*.googleapis.com` |
4444
45The first credential you add for a service from the **Connectors** tab is on in every workspace and channel as soon as you save it. To give it narrower reach, see [where a new connector applies](/docs/claude-tag/admins/add-connections#add-a-connection) before you save the connector. Click **Connect** to save the connector.
46
4547For Google Workspace data (Drive, Calendar, Gmail, Docs), the service account needs domain-wide delegation configured in your Google Admin console. In the service account's domain-wide delegation entry, list every scope you entered in **Scopes**, or `https://www.googleapis.com/auth/cloud-platform` if you left **Scopes** empty. Google's guide is at [developers.google.com/identity/protocols/oauth2/service-account](https://developers.google.com/identity/protocols/oauth2/service-account#delegatingauthority).
4648
4749Google refuses the token request when the domain-wide delegation entry is missing one of the requested scopes. Claude then reports HTTP 502 with a reason that starts with `injection failed ("<connection name>")`.
from line 52
5052
5153## Verify the connection
5254
53In a channel under the bundle's scope, in a new thread:
55In a channel where the connector is on, in a new thread:
5456
5557```text wrap theme={null}
5658@Claude what can you access from this channel?
5759```
5860
59Google Drive, Calendar, or Gmail appears in the list once the connection is live. New threads pick up the connection on their own; in an existing thread, ask Claude to use the service by name.
61Google Drive, Calendar, or Gmail appears in the list once the connector is live. New threads pick up the connector on their own; in an existing thread, ask Claude to use the service by name.
6062
61The credential row in the bundle shows **Never used** until Claude first uses the connection. The label tracks usage, not health, so a working connection stays on **Never used** until someone exercises it. To confirm the connection works, ask Claude in the same thread to read something from the service, such as today's calendar events or a named document. The label updates after that first read.
63To confirm the connector works, ask Claude in the same thread to read something from the service, such as today's calendar events or a named document.
6264
6365## Related resources
6466
No line in this hunk matches that.