Lesson 5.2 · D5 Configuration & Knowledge Management · 6 min
Manage uploaded knowledge and connectors
Keep one authoritative, current version of each source, and connect only what policy allows.
What the exam tests
Diagnosing inconsistent answers caused by stale or conflicting files, and the checks needed before enabling a connector.
Key ideas
- Replace, don't add
- When a price list or policy changes, replace the old file. Keeping both makes Claude draw on conflicting sources.
- Remove drafts and notes
- Discussion documents and superseded drafts introduce contradictions. Keep the approved version.
- Name and date files
- Clear file names with versions or dates make reviews quick.
- Connectors respect permissions
- A connector reaches what the connected user can access, not everything in the organisation. Data policy still applies to what is used.
- Before connecting
- Check policy approval and what the source contains (confidential, personal or client data). Limit access to the folders or channels that are needed.
Worked example
A Project still quotes old prices although the new price sheet was uploaded last week.
Weaker
Add an instruction telling Claude to prefer the newest file.
Stronger
Remove the outdated price sheet so only the current one remains.
Why: The cause is conflicting sources; fix the knowledge, not the wording.
Common traps
- Expecting Claude to “learn” new figures from users' corrections.
- Connecting an entire shared drive for convenience.
Remember
One current version per source; connectors only where policy allows.