How to set up Claude Projects for your team (and what most people miss)
In brief
Projects are the most underused feature in Claude. Here's how to configure them so your whole team gets consistent outputs — not whatever each person happens to type.
Contents
Most people use Claude the hard way.
Every conversation starts blank. Each person prompts differently. One person figures out the perfect way to get Claude to write a great brief — and that knowledge stays with them. Nobody else can reproduce it. The team has been "using AI" for months and has nothing to show for it beyond scattered individual wins.
Claude Projects are the fix. A Project is a persistent workspace with its own instructions, uploaded files, and conversation history. Write your context once, and it's there for every conversation inside that project, for everyone on the team.
Where Projects live now
Projects are in the Claude app on web, desktop and mobile. Since September 2026, Cowork is part of every Claude conversation, so a conversation inside a project can also work on files, run longer tasks and hand back documents. There is no separate Cowork project to keep in sync.
Claude Code works directly in your codebase, so it doesn't need a project: the code is already the context.
The new Projects with threads
There is also a newer kind of project, in public beta on Pro and Max since late 2026 and still rolling out. You find it at claude.ai/code or in the Code tab of the desktop app. You give the project a goal, and Claude acts as a coordinator: it turns each task you send into a thread that works in the cloud, keeps a project memory, and collects outputs in a library. It suits ongoing streams of work, especially code. Our guide to Projects with threads covers how it works and how we use it. The advice below applies to both kinds: a narrow goal works better than a broad one.
Who actually uses this
Marketing manager: uploads brand guidelines, campaign briefs, past copy. Every new conversation knows the voice, the audience, the product positioning. No more "here's our brand, now write me..." preamble every single time.
Customer success manager: one project per major account. Client background, past QBR notes, renewal history, stakeholder names. When a new CSM takes over an account, they're not starting from scratch.
Ops or HR manager: employee handbook, policy docs, SOP templates — all uploaded once. A project for people questions, a project for vendor comms. Consistent outputs across the team.
Developer: mostly working in Claude Code, so Projects aren't the main tool. But useful for non-code work — architecture planning docs, writing technical specs, research.
Executive: one project per initiative. Strategy docs, research, board prep. Context that persists week over week instead of being rebuilt every Monday.
One thing most people worry about
"What happens when I upload too many files?"
Nothing breaks. When a project's knowledge base grows large, Claude automatically switches to RAG mode — it retrieves only what's relevant to each question rather than loading everything at once. In practice, this means more files is fine. Upload the 80-page handbook. Upload the whole research archive. Claude figures out what to use.
Sharing requires a Team or Enterprise plan
On Free, Pro and Max plans, Projects are yours alone. You can set them up and use them personally, but you can't invite teammates.
On Team or Enterprise, you can share a project with specific people or make it visible to your whole organisation. You set the permission level: view only, full edit access, or owner. This is where the real compounding happens — one well-configured project becomes a shared resource rather than a personal shortcut.
The thing worth doing first
Don't build a general "work project". Build one for a specific use case: writing customer emails, running discovery calls, drafting performance reviews.
The narrower the scope, the easier it is to write instructions that actually work. Broaden it later if you need to. Start specific.
Try this today
Pick the task you re-explain to Claude most often. Make a project just for it, paste your usual explanation into the project instructions, and upload the two or three files you always attach. Next time, start the conversation inside the project and skip the preamble.