Configuring and Maintaining Claude Projects
Audience: professionals who use Claude at work, no coding or API knowledge needed. Verified = checked against Anthropic's documentation or help center on 2026-10-16. Design guidance = widely taught practice, not a documented rule.
What a Project is (verified, from the help center)
A self-contained workspace with its own chat histories and knowledge base. Inside it you can upload documents, provide context and have focused chats. Two main settings:
- Project knowledge: documents, text, code or other files Claude uses for background.
- Project instructions: guidance tailored to that Project (D5.1).
Facts to know:
- Projects are available on all plans; Free users can create up to five.
- On paid plans (Pro, Max, Team, Enterprise) projects scale with retrieval (RAG): when knowledge nears the context limit, Claude enables RAG to expand capacity by up to 10x while keeping quality.
- Team and Enterprise can share projects with Can view (see and chat, not edit) or Can edit (change instructions and knowledge, manage members) permissions, share with individuals, in bulk or organisation-wide; an Owner can disable public projects.
- Chat search is scoped: searching past chats within a project stays within that project.
- A new version of Projects is rolling out in beta (starting with Claude Code, where a project is one conversation with parallel cloud threads); the existing description applies to the current version. Check what your account has.
- Projects draw from your plan's usage like any other use of Claude.
Setting up well (design guidance)
- One Project per purpose (a client, a product, a recurring report), not one catch-all.
- Name it clearly and write a one-line purpose at the top of the instructions.
- Write instructions (role, audience, rules, format, uncertainty handling, examples).
- Upload only what is needed: current, authoritative, clean, well-named files (D5.3).
- Test with real questions, including ones whose answer is not in the knowledge, to see how Claude behaves.
- Decide sharing deliberately (who can view, who can edit).
Maintaining it
| Task | How often |
|---|---|
| Replace outdated documents; remove duplicates | Whenever sources change; review on a schedule |
| Re-read instructions for accuracy and conflicts | Monthly or after policy changes |
| Re-run a small test set of questions | After any change |
| Check who has access | Quarterly and when people leave |
| Name an owner responsible for upkeep | From the start |
Outdated knowledge is the commonest failure: Claude will cheerfully answer from an old policy.
Exam traps
- One giant Project for everything.
- Uploading outdated or contradictory files.
- No owner, so nothing is updated.
- Over-sharing edit access.
- Never testing after changes.
References
- What are projects? — checked Oct 16, 2026
Check your understanding
Same style guide and glossary needed in every weekly report chat. Where do they go?Show answerHide answer
Answer
In a Project's knowledge and instructions.What expands project capacity on paid plans?Show answerHide answer
Answer
Retrieval (RAG), up to about 10x.What is the commonest maintenance failure?Show answerHide answer
Answer
Stale documents and instructions nobody updates.