What you will be able to do
- Explain what a connector can reach, given source-system permissions, org enablement and action restrictions
- Connect Google Drive or Gmail for a workflow in the right order, from defining the need to checking the result
- Weigh the upload-versus-connector trade-offs of freshness, sharing, permissions and what gets read, knowing where Drive sync is and is not available
- Curate project uploads so retrieval finds the right document
- Keep connected knowledge current and free of noise by auditing, pruning, testing and managing connector load
Key concept
Inherited permissions — A connector never gives Claude its own view of a service: it acts with the signed-in person's access in that source system, so anything that person cannot open, Claude cannot reach either. Settings in Claude can narrow that access, but never widen it.
1.What a connector can and cannot reach
A connector lets Claude search, read and act inside a service such as Google Drive, Gmail, Slack or Linear, and the source system's permissions set the limits. If a person can't open a file, channel or record in the source, the connector can't reach it from Claude either. Custom connectors are the exception: one built on a shared credential reaches whatever that credential can access, whoever happens to be using it. That makes the choice of credential a decision about who sees what.
On Team and Enterprise plans, there are two more layers on top of source permissions. First, an Owner or Primary Owner has to add a connector for the organization before members can use it. Adding it only makes it available. Each person still signs in to the service themselves, unless the connector uses a shared credential. Second, Owners can set action restrictions for the whole organization. In Customize > Connectors, tool permissions are grouped by type, such as read-only tools and write/delete tools, and each one is set to Always allow, Needs approval or Blocked. One common pattern lets Claude search and summarize email but not send it. Another lets it read Drive files but not create or edit documents. Individual users can't override these settings.
The Google connectors read less than people expect. When Claude reads a Drive file, it extracts only the text, so a chart pasted into a Google Doc is invisible to it. In Gmail, Claude sees attachment metadata such as names, but not what the attachments contain. A workflow that depends on figures inside an emailed PDF won't get them through the Gmail connector. Actions with side effects ask first: by default, Claude asks for your approval before it sends, replies to or forwards email, or shares, moves or trashes Drive files. The exception is Auto mode, an approval setting in which these actions can run without asking, unless an automated check flags them as risky or your organization requires approval. That check can miss risky actions, so to approve each one yourself, use Manual or set the tool's permission to "Always ask" where that option exists. Auto mode is not the same thing as the Auto option under Tool access, which only decides how connectors are loaded into a conversation.
Checkpoint 1 of 7· Check yourself
A finance workflow depends on the totals inside PDF invoices that vendors send by email. With the Gmail connector turned on, a user asks Claude to add up this month's invoice totals. What can Claude get from those PDF attachments through the Gmail connector?
The Gmail connector returns attachment metadata such as names, not attachment contents. A workflow that needs the figures inside an emailed PDF won't get them through Gmail. The 'text only, no images' limit is a different rule. It applies when Claude reads a Drive file.
“Access email metadata, including attachment metadata (not attachment content)”Source: support.claude.com
Checkpoint 2 of 7· Check yourself
On a Team plan, an Owner adds the Google Drive connector for the organization. The connector does not use a shared credential. The next day, a member wants Claude to search their Drive files. What has to happen first?
Adding a connector at the org level only makes it available. Each person still authenticates with their own account, unless the connector uses a shared credential. Individual users also can't change org-wide tool permissions.
“Enabling a connector makes it available to your team, but it doesn't automatically grant anyone access.”Source: support.claude.com
Checkpoint 3 of 7· Exam question
A department head turned off the organization's 'Share chats that use connectors' setting. A team lead now tries to share a Project chat with a coworker, and the Project has synced Google Drive content. The share is not allowed. Why?
Correct answer: C — That setting prevents sharing chats that use connectors or synced content, including chats in a Project that has synced content.
- A. Incorrect: shared chats are not limited to uploads. The block comes from the organization setting, not a permanent lock on the Project.
- B. Incorrect: Drive folder sharing is a separate matter. The block here is caused by the organization setting.
- C. Correct: with the setting off, chats that use connectors or synced content cannot be shared, and that includes every chat in a Project with synced content.
- D. Incorrect: the setting covers all connector use and synced content, not only email sending.
2.Connecting Drive and Gmail for a workflow
Before you connect anything, write down what the workflow needs. Name the file or mailbox, and say whether Claude only reads or also writes. Connecting a service gives Claude permission to access, and possibly modify, data in it at your account's level of access. Defining the need first means you grant only that much access, and it gives you something concrete to check the result against later.
Once the need is clear, the setup follows a fixed order:
- Decide which source the workflow needs and what Claude should do with it.
- Go to Customize > Connectors, choose Google Drive or Gmail, click Connect, and sign in with your own Google account. Claude can only reach data in the account you connect.
- In the chat, open the + menu (or type /), hover over Connectors and switch the service on for that conversation. Then ask your question, naming the file if you know it.
- Check what came back against the source. Claude's answer cites the emails or documents it used, with links to the originals when they are available.
The last step catches problems the other steps can't. For example, Claude may read last quarter's copy of a spreadsheet instead of the current one. The citation shows which file was used, so a thirty-second comparison with the original confirms both the file and the figure. How much checking a given output deserves is covered in review depth and escalation.
If the connection fails, the fix depends on who is blocking it. If you see "You may need to reconnect with your Google Drive account," disconnect the connector in Customize > Connectors. You'll be asked to sign in to Google again the next time you use it. If the message says your institution's admin needs to review Claude, the block is on the Google side. A Google Workspace admin has to mark Claude as a trusted app in Google's API controls.
Checkpoint 4 of 7· Put it in order
A user wants Claude to pull this quarter's figures from a spreadsheet in their Google Drive. Put the setup steps in the order the workflow requires.
- 1.In the chat, open the + menu, hover over Connectors and switch Google Drive on for this conversation
- 2.Ask the question, naming the spreadsheet if you know it
- 3.Compare the cited document and figure in Claude's answer with the original in Drive
- 4.In Customize > Connectors, click Connect on Google Drive and sign in with your own Google account
- 5.Decide which Drive file the workflow needs and whether Claude only reads it or also writes to it
You define the need first so you grant only the access the workflow requires. A service has to be connected before you can switch it on in a chat. The citations in the answer then let you check that Claude used the right file, for example the current spreadsheet and not last quarter's copy.
“Once connected, services become available in your conversations”Source: support.claude.com
3.Upload versus connector: the trade-offs
A document reaches Claude in one of two ways: you upload a copy to a chat or to a project's Files section, or you connect its source and let Claude read the live file. The upload-versus-connector trade-off is first a matter of time. An uploaded file is a snapshot that stays exactly as it was on the day you added it. A Google Doc added from Drive syncs, so Claude works from the latest version. Upload something fixed, like a signed contract or a published policy PDF. Connect the source when the document is still being edited.
| Question | Uploaded file | Google Drive |
|---|---|---|
| Does it stay current? | No. It is fixed at upload time | Yes. Google Docs added to chats and projects sync from Drive |
| Can it go into a shared project's Files? | Yes | No. The Drive option is only available in private projects |
| Whose permissions apply? | Anyone in the project sees the uploaded copy | Each person's own Google permissions |
| What is read? | Text from most document types; text and visuals in PDFs of 100 pages or fewer | Text content only; embedded images are not processed |
Access cuts the other way. A connector reads through each person's own Google permissions, so a member who can't open the file in Drive gets nothing from it in Claude. An uploaded copy is visible to everyone the project is shared with, including Can view members, whatever their Drive access. That helps when a contractor needs one rate card without being let into the whole folder. It is a leak when the file was meant to stay restricted. Connectors carry a running cost too: each one takes up space in the conversation, while an upload costs only its own content.
The shared-project row decides most team setups. Adding Drive files to a project's knowledge works only in private projects, and the option is disabled in shared ones. A team project can therefore hold only uploaded copies, and someone has to refresh them by hand. For a document that changes every week, a shared project usually works better if members turn on the Drive connector in their chat and read the live file, each through their own Google access. Uploaded copies are better for reference material that rarely changes. How project sharing itself is set up is covered in project configuration.
Size limits shape the choice as well. You can attach up to 20 files to a chat. Files added to chats from Drive must fit in the conversation's context window. Project knowledge works differently on paid plans: as it nears the context window limit, Claude switches to RAG mode and uses a project knowledge search tool to pull in only the relevant passages, which raises capacity by up to 10x. Above that threshold, Claude finds documents by searching instead of holding everything at once, and the next section is about making that search work. How the context window is budgeted is covered in context and memory management.
Checkpoint 5 of 7· Check yourself
Your team works in a shared project. A pricing Google Doc that the project depends on is edited every week in Drive. Which setup keeps Claude working from the current version?
The Drive option for project Files works only in private projects and is disabled in shared ones. An uploaded copy stays as it was on the day it was added, so for a document that changes often, members should read the live file through the Drive connector with their own Google permissions.
“The Google Drive connector is only available when adding to Files in private projects. This option will be disabled for shared projects.”Source: support.claude.com
4.Curating what goes into project knowledge
Project knowledge is the only place where context carries from one chat in a project to the next. A fact mentioned in one conversation doesn't reach the others unless it is added to the project knowledge base. That's why what you put there matters. Each file you add becomes background for every chat in the project, whether or not it is relevant to that chat.
Curating a project mostly means helping retrieval. Clear file names help Claude find the right document. A name like "Q3-pricing-policy-v4.pdf" gives the search something to match, and "scan0042.pdf" does not. Put related documents in the same project so Claude can connect them. When you ask a question, naming the document helps Claude focus its search. Before you upload, also think about how each file will be read:
- Claude reads only the text in non-PDF documents, so a diagram inside a DOCX is lost. If the visual matters, upload it as an image or as a short PDF.
- PDFs of up to 100 pages are read for both text and visuals. From 101 to 1000 pages, Claude reads the text only.
- Very large documents are easier to work with when divided into smaller sections, which also gives each part a name the search can match.
- Images work best at 1000x1000 pixels or larger.
Checkpoint 6 of 7· Match them up
Match each problem in a project's knowledge base to the curation step that fixes it.
Tap a term, then the definition that fits it.
Curating project knowledge mostly means helping retrieval. Clear file names, smaller named sections and naming a document in the question all help Claude find the right source. Visuals in non-PDF documents are lost, so a diagram that matters has to be uploaded as an image or a short PDF.
“Well-named files help Claude understand and retrieve the right information more effectively.”Source: support.claude.com
5.Keeping connected knowledge current and free of noise
Uploaded knowledge goes stale without any sign. When the live document in Drive changes, the copy in the project doesn't. Claude keeps answering from the old version, and if the new version is uploaded next to it, the project holds two conflicting copies. Project content can be added or removed at any time, so the fix is routine maintenance, done in this order:
- Audit before deleting. List every uploaded file and compare each one with its current source. Mark the files that are outdated, duplicated or unrelated.
- Remove the marked files so old copies no longer sit next to current ones.
- Add current versions of the documents the project still needs. For documents that change often, use Drive instead: in a private project, add them from Drive so they stay in sync. In a shared project, rely on the connector in chat.
- Test in a fresh chat in the project. Ask a question whose current answer you know, and confirm the reply reflects the update.
A fresh chat matters in the last step because an older conversation may already contain the stale answer. A new chat in the project answers only from the project's current state. Diagnosing a project that has degraded more broadly, and telling the team about changes, are covered in configuration lifecycle and degradation.
Connectors can create noise too. Every connector you add takes up space in the conversation, so a large collection of connectors leaves less room for documents and conversation history. Tool access in the + menu offers three modes:
- Auto (the default): Claude decides which connectors to load based on the task.
- Always available: every connector loads at the start. This suits fewer than 10 connectors that you use constantly.
- On demand: connectors load only after Claude searches for the relevant one. This suits libraries of 10 or more, at the cost of an extra step.
Pruning applies to connections as well as files. Review what each service asks for when you connect it, and disconnect services you no longer use from Customize > Connectors. An unused connector still takes up conversation space and still holds access to your account.
Checkpoint 7 of 7· Match them up
Every connector you add takes up conversation space. For each Tool access mode in the + menu, pick how it loads connectors and when it fits best.
Tap a term, then the definition that fits it.
Always available spends conversation space up front so that every tool is ready at once, which pays off for a small set of connectors you use all the time. On demand saves that space for large libraries, but Claude has to find the right connector first. Auto is the default and lets Claude choose what to load for each task.
“On demand: Connectors aren't loaded until Claude searches for the right one based on your request.”Source: support.claude.com
Sources
(7)
Every claim above is drawn from one of these pages, quoted as it was written on the date shown.
- 1.https://support.claude.com/en/articles/11176164-use-connectors-to-extend-claude-s-capabilitiesOfficial docs
“Custom connectors that use a shared credential reach whatever that credential can access.”
↩︎ What a connector can and cannot reach“This includes every chat in a project that has synced content.”
↩︎ What a connector can and cannot reach“Only connect services you trust and need for your workflows.”
↩︎ Connecting Drive and Gmail for a workflow“Disconnect services you no longer need or use.”
↩︎ Keeping connected knowledge current and free of noise“Claude inherits each person's permissions from the connected service.”
↩︎ Key concept“Enabling a connector makes it available to your team, but it doesn't automatically grant anyone access.”
↩︎ Exam trap 1“Restricting actions in Claude never grants more access than the source system permits—it only narrows it.”
↩︎ Exam trap 5“Restricting actions in Claude never grants more access than the source system permits—it only narrows it.”
↩︎ Prediction“Enabling a connector makes it available to your team, but it doesn't automatically grant anyone access.”
↩︎ Checkpoint“Once connected, services become available in your conversations”
↩︎ Checkpoint - 2.
“When Claude reads a Google Drive file, it extracts text content only.”
↩︎ What a connector can and cannot reach“In Auto mode, these actions can run without asking you, unless an automated check flags them as risky or your organization requires approval.”
↩︎ What a connector can and cannot reach“Claude's response includes citations indicating which emails, calendar events, or documents were used as sources, with links to the originals when available.”
↩︎ Connecting Drive and Gmail for a workflow“Google Docs added to chats and projects sync directly from Google Drive, so you're always working with the latest version.”
↩︎ Upload versus connector: the trade-offs“Claude mirrors your existing permissions—you cannot access information you don't already have access to in Google Workspace.”
↩︎ Upload versus connector: the trade-offs“Attachment content is not directly accessible through Gmail (metadata only).”
↩︎ Exam trap 2“The Google Drive connector is only available when adding to Files in private projects.”
↩︎ Exam trap 3“Google Docs added to chats and projects sync directly from Google Drive, so you're always working with the latest version.”
↩︎ Exam trap 4“Access email metadata, including attachment metadata (not attachment content)”
↩︎ Checkpoint“The Google Drive connector is only available when adding to Files in private projects. This option will be disabled for shared projects.”
↩︎ Checkpoint - 3.
“Can view: Members can see project contents, knowledge, and instructions, and chat within the project, but cannot edit it.”
↩︎ Upload versus connector: the trade-offs - 4.
“Each connector takes up space in a conversation.”
↩︎ Upload versus connector: the trade-offs“Each connector takes up space in a conversation.”
↩︎ Keeping connected knowledge current and free of noise“On demand: Connectors aren't loaded until Claude searches for the right one based on your request.”
↩︎ Checkpoint - 5.https://support.claude.com/en/articles/11473015-retrieval-augmented-generation-rag-for-projectsOfficial docs
“Claude uses a project knowledge search tool to retrieve relevant information from your uploaded documents.”
↩︎ Upload versus connector: the trade-offs“Well-named files help Claude understand and retrieve the right information more effectively.”
↩︎ Curating what goes into project knowledge“Add and remove content at any time”
↩︎ Keeping connected knowledge current and free of noise - 6.
“Context is not shared across chats within a project unless the information is added into the project knowledge base.”
↩︎ Curating what goes into project knowledge - 7.
“consider dividing them into smaller sections to stay within limits.”
↩︎ Curating what goes into project knowledge