Skip to main content
Connections are added inside an Access bundle. At 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.
Connecting Google Drive and Calendar lets Claude read documents, spreadsheets, and calendar events from any channel under the bundle’s scope. You add it as a connection inside an Access bundle; the credential belongs to the agent, not to any person. This is an HTTP API connection, not a personal claude.ai connector. A member’s own Google connector applies only in DMs.

​
Choose OAuth or a service account

The connection picker offers two routes:
RouteWhen to use
OAuth (Connect button)Fastest path. An admin signs in with a Google account that has access to the content Claude needs.
GCP service-account keyWhen you want a dedicated non-human identity in Google with auditable access, or need domain-wide delegation across your Workspace.
Both 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).

​
Add the connection with OAuth

In the bundle, click Connect next to Google Drive or Google Calendar. A scope checklist appears with read-only scopes selected by default. Each scope grants a specific permission:
ScopeWhat it lets Claude do
openid, userinfo.emailIdentify the connected account (selected by default)
calendar.readonlyRead events and calendars
calendar.events.readonlyRead events only (narrower than calendar.readonly)
calendarCreate, edit, and delete events
drive.readonlyRead files and folders
drive.fileCreate and edit files Claude itself created
Check write scopes only if Claude should create or edit. Click Sign in with Google Calendar (or Sign in with Google Drive), approve the Google consent screen, and the credential is saved. The 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.

​
Add the connection with a service account

In the bundle, click Connect another app at the bottom of the Credentials tab, then choose GCP access token (with Service Account Key).
FieldValue
GCP service account key (JSON)The JSON key file from Google Cloud Console
Scopes (optional)The Google API scopes to request (for example https://www.googleapis.com/auth/drive.readonly). The field is labeled optional, but Drive and Calendar calls fail without the matching scope listed here.
Subject (optional)A user email to impersonate via domain-wide delegation. Set this for Workspace data (Drive, Calendar, Docs).
Allowed websites*.googleapis.com
For Google Workspace data (Drive, Calendar, Docs), the service account needs domain-wide delegation configured in your Google Admin console with the matching API scopes. Google’s guide is at developers.google.com/identity/protocols/oauth2/service-account. The Agent Proxy injects the credential at the network boundary; the model and the sandbox are not given the key. See how Agent Proxy works.

​
Verify the connection

In a channel under the bundle’s scope, in a new thread: 
@Claude what can you access from this channel?
Google Drive or Calendar appears in the list once the connection is live. New connections apply to new threads only.