An HR business partner is configuring a new Project for recurring policy questions from managers. The Project will be used across many chats by several HR team members.
Which content belongs in the Project knowledge base?
A.
the current employee handbook plus prior versions of the handbook going back five years, so Claude can answer questions about how policies have changed
B.
the current employee handbook, the leveling guide, the policies-FAQ, and every email the HR team has sent about policy in the past year, for additional context
C.
the current employee handbook only, with the leveling guide and the policies-FAQ attached at the start of each chat as needed for that chat ' s topic
D.
the current employee handbook, the leveling guide, and the policies-FAQ document referenced across the Project ' s chats
Under the objective Configure Claude Projects with instructions and knowledge sources, the project knowledge base is designed to store authoritative, canonical, and frequently accessed reference material that remains stable across multiple chat sessions.
Option D accurately selects the core, evergreen operational documents required for recurring HR inquiries—the current active handbook, leveling framework, and standardized FAQ. Including outdated handbooks (Option A) risks hallucination and policy contradictions because Claude might cite obsolete rules. Uploading raw email trails (Option B) injects uncurated conversational noise, conflicting statements, and potential privacy leaks into the persistent context. Relegating essential, standard documents to manual per-chat uploads (Option C) undermines the primary efficiency benefit of Claude Projects, which is to eliminate repetitive context uploading across team workflows.
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit