Home › Study guides › CCAO-F › Domain 5 › Lesson 5.2

CCAO-F · Domain 5 · 12% of the exam · Lesson 5.2 · 18 min read

Uploads and connectors: managing what Claude can read

When to upload a file and when to connect Google Drive or Gmail, what a connector can reach, and how to keep Claude's sources approved, current and scoped.

Written against objective 5.2 of the official CCAO-F exam guide (Version 1.0, effective July 2026). An independent resource, not affiliated with Anthropic; the practice questions are written from scratch.

5.2.1 Why a polished brief can be four months out of date

It's Tuesday afternoon, and on Thursday you have a renewal call with Fernbrook Veterinary Group. You lead the customer success team at a company that sells scheduling software to animal clinics on annual subscriptions. In May you set up your own Renewals Project, a Claude workspace that keeps files and instructions together for recurring work. Now you open it and ask Claude for a brief: what Fernbrook pays today, what renewal would cost, and which onboarding steps to offer their two new clinics.

The brief looks ready to use, and it is wrong in three ways. It prices the Growth plan at $42 per seat, from the price list PDF you uploaded in May; finance raised it to $46 in July. It recommends a kickoff workshop that your onboarding playbook dropped two weeks ago. And it says nothing about Fernbrook's complaints about double bookings, because those sit in a long email thread Claude has never seen.

Claude didn't misread anything. It worked from what it had: the May price list, the copy of the playbook you uploaded with it, and no email at all. It has no way to tell that a file has gone stale, so whatever you put within its reach, it treats as the facts.

So managing Claude's knowledge means deciding what to put within reach, and in which form. An upload gives Claude a copy of a file as it was when you added it. A connector links Claude to a live source, such as Google Drive, Gmail, Google Calendar or Microsoft 365, through your own account.

5.2.2 A copy or a live connection

Here is the question behind most knowledge setups: should Claude get a copy of this information, or a connection to where it lives? Two things decide it: how often the information changes, and where its source of truth lives, meaning the one place its owner keeps the approved, current version.

Think of a printed train timetable and the departures board at the station. The printout is accurate on the day you print it and stays as printed when the schedule changes; the board shows what is running now. An upload is the printout: a copy that does not change when the original does. A connector is the board: each time Claude looks, it reads the source as it is at that moment.

The first two rows are the ones to remember; the other two follow from them.

Now sort the renewal work. Finance issues the price list as a new PDF each quarter, and that PDF is the source of truth, so an upload suits it. What failed wasn't the upload but the fact that nobody replaced it in July. The playbooks change weekly in Drive, so any copy is out of date within days. And customer emails aren't a document at all; they call for the Gmail connector.

5.2.3 What a connector can reach, and what it cannot

It's tempting to picture a connector as Claude getting its own key to the company's systems. It doesn't work that way. Claude uses the connector through YOUR account and inherits your permissions: if you can't open a file, channel or record in the connected service, Claude can't reach it either.

That rule cuts both ways. Claude can't read a colleague's inbox, but it can reach everything your own account can open, including folders someone shared with you years ago. Other gates stand in front of it too. On Team and Enterprise plans, a connector appears only once an Owner, an administrator of your organisation's Claude account, enables it. Each person then signs in with their own account, and Claude can use the connector only in conversations where it is switched on.

Connectors can do more than read, and each one differs. Anthropic's Help Center lists drafting, sending and replying to email among Gmail's abilities, and creating events among Google Calendar's; by default, Claude asks for your approval before each send. An Owner can also restrict a connector for everyone, for example letting Claude search and summarise email but not send it. These abilities change as the product changes, so check the connector's page in the Connectors Directory, Claude's list of available connectors, rather than assume.

The Fernbrook thread shows these limits at work. Part of it went between Fernbrook's practice manager and Tariq, your account executive, without you in copy, so those messages aren't in your mailbox and aren't within Claude's reach. Claude also sees that an email has an attachment, but not what the attachment contains. The signed order form from March stays unread unless you add it yourself.

5.2.4 Drive files in the Project, or Drive search in a chat

Google Drive gives you two ways to bring a document in, and they behave differently. The first is to pick specific files and add them to a Project's knowledge, the files every chat in it can draw on. A Google Doc added this way stays linked to the original: its content refreshes from Drive from time to time when you open the Project. Edits reach Claude without a re-upload, though not necessarily the minute you make them.

The second is to switch the Drive connector on in a conversation and ask. Claude searches your Drive and reads whatever it judges relevant, so the choice of file is Claude's. Your Drive holds drafts, old copies and colleagues' notes, and a search can surface any of them. It's the difference between handing a new colleague the three documents they need and giving them the key to the filing room.

For the renewal work, you remove the May playbook copy from the Project and add the current playbooks from Drive, so onboarding questions start from them. Drive search stays useful for the other job: "find the case study we wrote for a clinic group last year." Either way, Claude reads a Doc's text but not its images. A step shown only as a screenshot needs words too.

5.2.5 Keep the knowledge approved and current

Here is the belief behind many wrong answers: the more files Claude can see, the better it answers. More files help only when you would want Claude to follow every one of them. Put the May price list next to the July one and Claude has two prices for the Growth plan and nothing that says which one counts. It may use either, or blend them. Four habits keep the knowledge trustworthy.

1. REMOVE outdated, duplicate and conflicting files. A superseded version kept "for reference" is still a source Claude can use.
2. NAME files with a version or date and a status such as APPROVED. Clear, descriptive names also help Claude find the right file.
3. SEPARATE drafts from the knowledge that answers must follow. A draft stays with its author until it is approved.
4. CONFIRM with the owner before a newer or unfamiliar source replaces the approved one.

Here is the Renewals Project's knowledge before and after a clean-up. Look at what each new name tells you, and at what has gone.

BEFORE
Price list.pdf (uploaded in May)
Price list (1).pdf (the same file, uploaded twice)
Pricing ideas - Lena.docx (a proposal, never approved)
Onboarding playbook.pdf (a copy from May)

AFTER
Price list 2026-Q3 - APPROVED by Finance.pdf
Onboarding playbooks (linked from Drive)

The fourth habit is the easiest to skip. A sales colleague emailed last week that clinic groups get 10% off this quarter, and the Gmail connector can find that email. That doesn't make it pricing policy. Until finance, which owns the price list, confirms the discount, the approved list governs and the discount goes to finance as a question. When sources conflict and you can't tell which one governs, don't ask Claude to pick: ask the owner.

5.2.6 Connect only what the task needs, and check the source

Connecting a mailbox or a drive is not like attaching one file. It brings everything your account can open within Claude's reach: HR conversations, customers' personal details, contract terms. What you connect sets the outer limit of what a vague request could pull in. That is why Anthropic's advice is to connect only services you trust and need, and to disconnect those you no longer use.

For the renewal work, that means three decisions. Connect only sources your company has approved and the task needs, here Gmail and Drive, not personal accounts or apps you're trying out. Keep Gmail switched on only in the chats where you prepare calls. And ask narrowly: one customer, a date range, a topic. Your organisation's data rules decide what may go into Claude at all; this habit keeps the reach no wider than the task.

Last, check where an answer came from. With the Google connectors, Claude's answer cites the emails or documents it used, with links to the originals where available. For Project files, ask Claude to name the file behind each point, then open it. Confidence is not evidence: in a summary, a draft that sounds certain looks just like the approved version. In the Fernbrook request below, look at the last three lines: prices come from one named file, conflicts are listed rather than settled, and every point names its source.

Find my emails with Fernbrook Veterinary Group from the last three months about their renewal or the double-booking problem.
Summarise them for Thursday's renewal call: open issues, anything we promised, and anything they asked for in writing.
Take prices only from "Price list 2026-Q3 - APPROVED by Finance" in this Project, never from prices quoted in emails. If an email mentions a different price or a discount, list it under "To confirm with Finance".
After each point, name the email (sender and date) or the file it came from.
If something is not in the emails or the files, say so instead of filling the gap.

5.2.7 The exam traps

Every trap in this objective mistakes reach for authority, or a copy for the live source.

• ✗ Uploading a copy of a document that changes every week, then forgetting it. ✓ Link the live source through a connector. Upload only what is stable, and replace the copy when its owner issues a new version.
• ✗ Leaving old and new versions side by side so Claude "has everything". ✓ Remove superseded, duplicate and draft files, because Claude cannot tell which one you meant.
• ✗ Treating the newest file, a connector result or an email as the new rule. ✓ The approved version governs. When sources conflict and you can't tell which one counts, keep the approved one and ask its owner.
• ✗ Connecting every available tool "so Claude has full context". ✓ Connect the approved sources the task needs, and switch them on only where they are needed.
• ✗ Telling Claude to "use the latest information" to fix a wrong answer. ✓ Fix the knowledge itself. An instruction cannot correct a stale or unapproved file that is still within reach.
• ✗ Disconnecting everything after one answer drew on a draft. ✓ Narrow the reach and curate the sources. The connector was not the problem; what it could see was.

5.2.8 Put it together: manage what Claude can read

You now have the whole method. Choose a copy or a connection, know what a connector can reach, and pick the files Claude should follow. Keep the knowledge approved and clearly named, connect only what the task needs, and check the source. The quickest way to make it stick is to watch a stale copy mislead Claude, then fix it.

The rest of Domain 5 builds on this. System-level instructions (5.3) can hold a standing rule about sources, such as "follow approved files and list conflicts for the owner", so you stop repeating it in every request. Keeping knowledge current over months, with a review rhythm and a way to handle changes, is the subject of maintaining configurations (5.4). And what data may go into Claude at all belongs to Domain 6 (6.2 and 6.3).

Key takeaways

• ✓ Claude treats whatever is within its reach as the facts, so what you upload and connect decides what it can get right.
• ✓ An upload is a copy frozen when you add it and a connector reads the live source, so choose by how often the information changes and where its approved version lives.
• ✓ A connector works through your account: Claude reaches only what you can open, only where the connector is switched on, and within what your organisation allows.
• ✓ Drive files added to a Project stay linked to the original, while Drive search lets Claude choose, which suits finding material rather than deciding what governs.
• ✓ Remove outdated, duplicate and draft files and name the rest with version, date and status, because newest or most reachable is not the same as approved.
• ✓ Connect only approved sources the task needs, and check the file or email each answer came from before you rely on it.

Check your understanding

4 questions written for this lesson, then one from the CCAO-F question bank on the same topic. Every answer option is explained, including the ones you did not pick. Nothing is stored.

Sources

• Use connectors to extend Claude's capabilities
• Use Google Workspace connectors
• Google Drive connector
• Get started with connectors
• Upload files to Claude
• Retrieval augmented generation (RAG) for projects
• The CCAO-F exam guide, summarised