Task statement 5.1 · Configuration and knowledge management
5.1 · Configuring Projects
In Wrenfield Housing, the course example, the communications team writes its tenant letters in the Tenant comms Project from 3.1. A Project, a workspace whose chats all start from the same files and guidance, only helps when it is set up for one job. Filled with every file anyone had, it hands Claude old rules next to current ones, and the drafts mix them up.
share
The tempting setup is one Project for the whole team, with every file anyone might need, because more knowledge feels safer than less. Claude cannot tell a superseded handbook from the current one, or a staff rule from a tenant rule, unless the setup tells it, so the extra files turn into wrong answers rather than spare ones. The same instinct puts the Project's purpose in its description, which Claude never reads.
KnowledgeWhat a Project holds, and how you set one up
A Project has its own chats and two settings that every chat in it starts from. Project knowledge is the set of files you add to the Project. Project instructions are the guidance Claude applies to every chat inside that Project, and to no chat outside it. The name and description help colleagues find the Project, but Anthropic's help article says Claude has no access to them, so a purpose written only there never reaches Claude. This rules out any answer that expects a Project's name or description to steer Claude's drafts.
Setting up a Project takes four steps, starting from Projects in the sidebar and "+ New Project":
- Create and name it for one recurring purpose: a job that comes back, such as weekly tenant letters, not a team's whole workload.
- Add project knowledge: only the current files that purpose needs, and nothing your policy keeps out of Claude, such as personal data.
- Set project instructions: the purpose, the audience and the rules every chat must follow.
- Share it: on a Team plan, choose the people and give each one "Can view" or "Can edit".
Interactive · what each part of the Project gives the drafts
Step through the Tenant comms Project, from the first one-for-everything attempt to the rebuilt setup, and see what each part gives the drafts.
One for everything: a Project called Comms held five files, including two handbooks and the repairs triage guide, under a one-line instruction, and all eight members could edit it. Drafts mixed old and current rules.
Focused: one purpose, tenant letters and notices, with only the style guide and the 2025 handbook. Drafts now use current files, but nothing tells Claude who the letters are for.
Instruction added: the purpose, the audience and the three style decisions from 3.4 reach every chat. Any of the eight members can still change the files.
Shared at the right level: the lead and one officer can edit, and the other six view and draft. The setup changes only when its owners change it.
Project knowledge takes the document types Claude reads in a chat, such as PDF, Word (DOCX), plain text and CSV files. Each file can be up to 30 MB, and there is no cap on the number of files. From most files Claude extracts only the text, so a chart inside a Word file is lost, while a PDF of 100 pages or fewer is read with its charts and images. The total is bounded by the context window, the limit on how much Claude can work with at once (3.4). On paid plans, when project knowledge nears that limit, the Project switches to RAG (retrieval augmented generation). Instead of reading every file, Claude uses a project knowledge search tool to pull what a request needs, which can expand the Project's capacity up to ten times. Claude then sees only what the search returns, so an old file that matches a request well can supply the answer instead of the current one. More files are therefore never free.
Large knowledge depends on the plan. RAG for Projects is on Pro, Max, Team and Enterprise plans, not Free (checked 2026-10-15). A Project shows an indicator while it uses RAG, and it goes back to reading the files in full if the knowledge shrinks below the limit.
KnowledgeSharing at the right level
On Team and Enterprise plans, "Share project" adds colleagues by name or email, each with a permission level, unless an owner has turned project sharing off for the organisation. The level matters because a Project's files and instructions shape every colleague's drafts, so anyone who can edit them can change everyone's results. Give "Can edit" to the people who own the setup, and "Can view" to everyone who only drafts in it. The two levels differ like this:
Can view
The member sees the Project's knowledge and instructions and chats in the Project, but cannot change it.
Fits: writers who need the setup but do not maintain it.
Can edit
The member also changes the instructions and knowledge, and manages the Project's members.
Fits: the few people responsible for what the Project holds.
SkillWorked example: rebuilding the Tenant comms Project
The team's first attempt was a Project called "Comms", meant for everything the communications team does. All eight members could edit it, so the knowledge grew to every file anyone had, and the only instruction was the one line from 3.1. Within a month, the letters mixed versions and rules:
# before: Project "Comms", all 8 members Can edit Knowledge: style guide, handbook 2023, handbook 2025, annual report 2024–25, repairs triage guide Instructions: Follow the style guide in every letter. → "report a repair by phone or letter" (2023 handbook; no online form) → "urgent repairs: within 24 hours" in a tenant notice (triage guide) # after: Project "Tenant comms"; lead + 1 officer Can edit, 6 Can view Knowledge: style guide, tenant handbook 2025 Instructions: This Project drafts letters and notices for our tenants. Plain English. Say "tenants", never "customers". Sentences of 20 words or fewer. Give each figure its period and source. → repair routes and wording match the current handbook and style guide
The cause was the setup, not the model. Two handbooks gave two answers on how to report a repair, the triage guide carried rules written for staff, and the one-line instruction never said who the letters were for. The fix gave the Project one purpose and a name to match. The 2023 handbook and last year's report came out, and the triage guide stayed only in the Repairs Project (4.4), where its job is. The instruction now states the purpose and audience and keeps the three style decisions from 3.4. Writing instructions well is 5.3, and keeping files current is 5.4. No file with tenants' personal data goes in, as the AI policy requires, and the communications lead still checks each letter.
- A Project's purpose reaches Claude only through its instructions; the name and description are for people.
- Project knowledge holds the current files for one job, because extra versions and other teams' guides become wrong answers.
- On a Team plan, "Can view" lets colleagues draft in a Project; "Can edit" is for the people who keep it.