Task statement 5.2 · Configuration and knowledge management
5.2 · Knowledge and Connectors
In Wrenfield Housing, the course example, the communications team's Tenant comms Project answers from the tenant handbook and style guide it holds as knowledge (3.1). When the original documents change but the Project's copies do not, Claude answers confidently from an old version, and a wrong fact can reach a tenant letter.
share
The tempting assumption is that knowledge added once stays current, because the file in the Project and the document in Drive share a name. An uploaded file is a copy, so Claude keeps answering from it after the original changes, and nothing in the reply says the copy is old. The opposite mistake is to connect every source, such as a shared inbox, because more context feels safer. A connector, a link that lets Claude read, and sometimes act in, another service (4.1), reaches whatever the connected account can open, so a mailbox full of tenants' details becomes something Claude can read.
KnowledgeTwo ways knowledge reaches Claude
Knowledge reaches Claude in two ways. Uploaded knowledge is a file you add from your computer, such as a PDF of the handbook, to a chat or a Project's files. Claude reads the copy you added, so when someone edits the original, the copy stays as it was until a person replaces it. A connector works the other way round: Claude fetches from Google Drive or Gmail when a request needs it. Google Docs added from Drive sync directly from Drive, so Claude works with the latest version. This rules out any answer that expects an uploaded file to update itself.
Uploads also need tidying, because Claude cannot tell which of two similar files you meant. Three things stay out of a Project's knowledge: duplicates, which give the same facts twice; outdated versions, which give old facts next to new ones; and files with personal data, because whatever sits in knowledge is read in every chat there, which breaks Wrenfield's AI policy rule 1. On a Team plan, connectors then add their own controls, in this order:
- The owner enables it: an Owner or Primary Owner turns Google Drive and Gmail on for the organisation. Until then, nobody can connect them.
- Each person connects their own account: enabling a connector gives nobody access by itself; each member signs in to Google separately.
- Claude uses that person's permissions: it mirrors what they can already open in Google Workspace, and nothing more.
- The chat turns it on: in each conversation, the person switches on the connectors that chat needs, from the + menu under Connectors.
Where Drive files can be added matters as much. A shared Project is one you have shared with colleagues through "Share project" (5.1). The Help Center says the Drive option for adding to a Project's files is disabled in shared Projects, so a shared Project's files are uploads only. The live Drive Doc goes into a chat instead, through the + button and "Add from Google Drive". In a private Project, you can add it through Files, + and "Drive".
Interactive · which copy of the handbook Claude reads
Follow the handbook from January to March and see which version Claude reads in each place.
Uploaded file: the January PDF in the shared Project has no link to Drive. After February's edit, Claude still gives the old hours, with nothing to say they are old.
Drive Doc in a chat: the Doc syncs from Drive, so February's edit reaches the chat and Claude gives the new hours.
Replace the upload: in February the editor removes the January file and uploads the current one. The answer is right again, but only until the next edit in Drive.
KnowledgeWhat each Google connector reads and does
The two Google connectors reach different things. Google Drive lets Claude search and read Google Docs, and read Sheets, Slides, PDFs and Office files. It takes the text from them, but not images inside documents. Gmail lets Claude search and read email, draft messages, and send, reply or forward. By default it asks your approval before each of those actions (4.4). Gmail sees only the metadata of attachments, such as their names, not their content. Before you connect either one, ask whether everything that account can open is fit for Claude to read:
A stable file a shared Project needs, such as the style guide, with one person named to replace it when it changes.
Wrong choiceUploading a file that changes weekly and trusting it to stay current.
A living document or your own mailbox, read in a chat or private Project with your own permissions.
Wrong choiceExpecting the Drive option in a Project shared with the team.
A source full of personal data, such as a shared inbox of tenants' enquiries, under a policy that bans it.
Wrong choiceConnecting it and telling Claude in the prompt to ignore names.
SkillWorked example: the handbook that went out of date
The Tenant comms Project is shared with the communications team's eight members, so every writer uses the same knowledge. Its handbook was uploaded as a PDF in January. In February, the Drive copy changed: the repairs line now opens 8:00–19:00 on weekdays, the new hours the spring newsletter announced. In March an officer asked the Project for the hours:
# before: Project knowledge, March Tenant handbook 2025.pdf uploaded January Tenant handbook 2025 (1).pdf duplicate, uploaded January Style guide.pdf → "The repairs line is open 8:00–17:00 on weekdays." # after: the communications lead (Can edit) replaces the files Tenant handbook 2025, February.pdf old copy and duplicate removed Style guide.pdf re-checked against Drive → "The repairs line is open 8:00–19:00 on weekdays."
Claude was right about the file it had. The PDF was a January copy, so February's edit never reached it. The team wanted to add the Drive Doc instead, but the Drive option is disabled because the Project is shared. So the communications lead, who has Can edit, removed both January copies and uploaded the current handbook with its month in the name. Nobody was named to do it again after the next change, which is where 5.4 begins. Officers who want the live version add the Drive Doc to their own chat instead.
The team also decided what not to connect. The shared tenant-enquiries inbox holds tenants' names and addresses, so nobody connects it to Claude, under AI policy rule 1. A communications officer uses the Gmail connector only on their own mailbox, for their own drafts, such as a note to the contractor confirming the Millbrook servicing dates, 3–14 March.
- An uploaded file is a copy: when the original changes, someone must remove the old file and upload the new one.
- Google Docs added from Drive sync, but the Drive option for a Project's files is disabled in shared Projects.
- A connector reads everything the connected account can open, so a source full of personal data stays unconnected.