5.2 — Managing Uploaded Knowledge and Connectors

CCAO-F Domain 5 · Task 5.2

What You Need to Know

A Project’s knowledge arrives by one of two routes. The choice turns on how the material changes.

Route	Properties	Best for
Upload	Snapshot taken on the day of upload; stable and predictable; goes stale silently	Stable reference documents (terms, policies, handbooks)
Connector	Links to the live source (e.g. Google Drive); always the latest version; carries live mess	Material that changes frequently (schedules, rotas, living docs)

Permissions and Governance

On Team and Enterprise plans, an Owner or Primary Owner must enable connectors for the organisation before members can use them. Access mirrors what each person already holds in the connected service. Connectors can take actions (e.g. send email); by default Claude asks for approval before each action.

Retrieval, Not Cover-to-Cover Reading

Claude searches project knowledge and loads only the most relevant content. Clear, descriptive file names help. Name a specific document in your prompt to focus the search. Curation beats completeness: every document that is never needed dilutes the search space.

Key Concept: Upload-versus-connector items are keyed on how the material changes, never on how important it is.

Exam Traps

• Bringing in the whole shared drive so nothing is missing
• Choosing between upload and connector by how important the material is
• Having a Team-plan user switch on an organisation connector themselves