Option B is correct because Claude Projects are specifically designed to organize recurring work around persistent instructions and reference knowledge. Anthropic explains that documents uploaded to a Project’s knowledge base become available as context across chats in that Project. Project instructions likewise establish consistent guidance for Claude’s behaviour and responses. Team and Enterprise users can share Projects with other organization members using appropriate view or edit permissions.

A Google Drive Connector can retrieve information from connected files, but it is not the best primary answer for a curated workspace with stable instructions and a defined knowledge base. An Artifact is an editable output surface rather than a persistent multi-chat reference repository. Reattaching the same documents to every chat would work technically, but it creates unnecessary repetition and increases the risk that a team member forgets a required source or uses an outdated version.

The Project should contain only current, authoritative versions of the handbook, leveling guide, and FAQ. Access permissions and document maintenance responsibilities should also be defined. Therefore, a shared Project is the feature that most directly meets the stated multi-chat, multi-member requirement. See Anthropic’s documentation on creating and managing Projects and Project capabilities.

================