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.

Why it's tested

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":

  1. Create and name it for one recurring purpose: a job that comes back, such as weekly tenant letters, not a team's whole workload.
  2. Add project knowledge: only the current files that purpose needs, and nothing your policy keeps out of Claude, such as personal data.
  3. Set project instructions: the purpose, the audience and the rules every chat must follow.
  4. 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

Four parts of the Tenant comms Project on the left, each with an arrow to what it gives the drafts on the right. The purpose and name decide the job every chat is for. The knowledge decides which handbook and whose rules the drafts use. The instructions decide who the letters are for and which style rules hold. Sharing decides who can change the setup. A part still set up the first, one-for-everything way is dashed and labelled as such, and what it gives the drafts is dashed and labelled mixed up. THE PROJECT WHAT THE DRAFTS GET Purpose and name Tenant comms: letters and notices to tenants Comms: everything the team does FIRST SETUP FOCUSES BLURS CLEAR MIXED UP the job every chat is for → EVERY TASK IN ONE PLACE Project knowledge style guide, tenant handbook (2025) 5 files: 2 handbooks, old report, repairs triage guide SUPPLIES MISLEADS CLEAR MIXED UP which handbook, whose rules → OLD REPAIR ROUTES, STAFF RULES Project instructions purpose and audience, the 3 style decisions (3.4) Follow the style guide in every letter. STATES LEAVES OUT CLEAR MIXED UP who reads it, which rules hold → READERS AND PURPOSE GUESSED Sharing lead + 1 officer: Can edit 6 writers: Can view all 8 members: Can edit FIRST SETUP GUARDS OPENS CLEAR MIXED UP who can change the setup → ANY FILE, ADDED BY ANYONE Each part left in its first setup feeds the drafts something they should not use.

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.

Dashed and labelled MIXED UP: that part is still the first setup. Solid and labelled CLEAR: the rebuilt Project settles 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:

For people who draft in it

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.

For people who keep 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.

Ask one question: does each file and each line in this Project serve the one recurring job it is named for? Yes → keep it, and share at "Can view" unless the person maintains the setup. No → take it out, or move it to the Project whose job it serves.
Takeaway
  • 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.

check yourself

0 / 3 answered

A legal operations coordinator creates a Project for drafting supplier agreements and writes in its description: "For UK suppliers; use UK English and our standard liability cap." The colleagues who draft in the Project start fresh chats each day, and the drafts keep using US spelling with no liability cap.Which change most directly fixes this?

Select one.

A finance manager shares a month-end reporting Project with ten analysts on the organisation's Team plan, all at Can edit. Last month an analyst replaced the approved chart-of-accounts file with a draft. The analysts must keep drafting reports in the Project, and only the manager and their deputy should be able to change its files or instructions.Which TWO changes best protect the setup while keeping the analysts drafting?

Select two.

An HR coordinator runs one Project, "HR", for job adverts, staff policy questions and interview question sets, with every related file as knowledge. Adverts now read like policy text, and policy answers sometimes quote an advert's benefits. Each job recurs weekly with its own files and tone, and new staff use the Project without training.What is the most effective way to restructure this setup?

Select one.

sources

  1. Claude Help Center, "How can I create and manage projects?": "+ New Project"; Claude has no access to the name and description; private or organisation visibility on Team and Enterprise; adding knowledge with "+"; project instructions apply to all chats in the Project; "Share project" with "Can view" and "Can edit" and what each allows. Checked 2026-10-15.
  2. Claude Help Center, "What are projects?": Projects on every plan; sharing with members of the organisation on Team and Enterprise; owners can turn project sharing off; RAG on paid plans when knowledge approaches the context limit. Checked 2026-10-15.
  3. Claude Help Center, "Upload files to Claude" (updated 2026-07-23): supported document types; project files up to 30 MB each, unlimited in number within the context window; text extraction only, except PDFs, whose visual elements are read up to 100 pages. Checked 2026-10-15.
  4. Claude Help Center, "Retrieval augmented generation (RAG) for projects" (updated 2026-09-10): the project knowledge search tool; Pro, Max, Team and Enterprise plans; automatic activation near the context limit; up to 10x capacity; the indicator; switching back. Checked 2026-10-15.
  5. Wrenfield's "Comms" Project, its five files, the 2023 and 2025 handbooks and the sharing levels are this course's example.