Claude ChatLesson 6

Projects

Projects group related conversations. Upload files and set instructions once; every chat in the project uses them. Team Projects share that setup with colleagues.

Organizing conversations under a Project

Without Projects, every chat in Claude lives in a flat list — suitable for one-off questions, but hard to manage when you work on the same topic over days or weeks. A Project gives that work a home.

Create a project for each ongoing area — a client account, a product launch, a course you are writing — and start new chats inside it. All conversations stay grouped and easy to find.

claude.ai
Projects
📣
Marketing Copy
4 chats
Contract Review
Python Tutoring
Q2 Analysis
📣
Marketing Copy
All brand and campaign writing in one place
+ New chat in project
Conversations
Draft Q3 marketing emailToday
Review blog post toneYesterday
Social media captions3 days ago
Product launch copyLast week
A Project groups related conversations — each chat stays organized under one topic
Example: A marketing team creates a "Campaign Q3" project. Every email draft, social post, and ad copy chat lives inside it instead of scattered across the general chat history.

Adding files and custom instructions

Each Project has two setup areas that apply to every chat inside it:

📁
Project files

Upload PDFs, spreadsheets, docs, and images once. Claude can reference them in any conversation within the project — no re-uploading each time.

📋
Custom instructions

Set a system prompt that tells Claude how to behave — tone, format, role, rules. Every new chat in the project starts with these instructions already in place.

Project settings — Marketing Copy
📋 Custom instructions
"You are a marketing copywriter for Acme Corp. Use a friendly, professional tone. Always keep headlines under 10 words. Reference our brand guide for colour and voice rules."
📁 Project knowledge — uploaded files
📄brand-guide.pdf1.2 MB
📊product-features.csv84 KB
📝approved-taglines.docx45 KB
+ Add files to project
Every chat in this project shares the same custom instructions and uploaded files

Example custom instruction

"You are a legal assistant reviewing contracts for a SaaS company. Flag missing liability clauses, ambiguous payment terms, and non-standard IP language. Always respond in bullet points."

Persistent context across sessions

In a regular chat, uploaded files and custom instructions do not carry over to the next conversation. In a Project, your files and instructions stay put — every new chat inside the project can use them.

Regular chatProject chat
Uploaded filesLost when chat endsAvailable in every project chat
Custom instructionsMust repeat each timeSet once, always active
Conversation historyIsolated per chatGrouped under the project
Best forQuick one-off tasksOngoing, multi-session work
Persistent context — files and instructions carry across every chat in the project
1
Monday
Uploaded brand-guide.pdf and set custom instructions
2
Tuesday
New chat — Claude already knows the brand voice (no re-upload)
3
Friday
Another new chat — files and instructions still active
✓ Unlike regular chats, you set up files and instructions once — every new conversation in the project starts with that context.
Projects remember your setup across sessions — no need to re-upload or re-explain each time

Team Projects for collaboration

Team Projects (available on Team and Enterprise plans) extend Projects to your whole organization. Multiple people can access the same project, share files and instructions, and see each other's conversations.

→
Shared files — Upload brand guides, templates, or datasets once — the whole team references the same sources.
→
Shared instructions — One set of custom instructions ensures every team member gets consistent Claude behaviour.
→
Shared conversations — Team members can read and continue each other's chats — useful for handoffs and review.
→
Access control — Project owners manage who can view or edit the project and its contents.
🤝
Team Project — Product Launch
Shared by 3 team members
Team
Members
A
Alex
Owner
P
Priya
Editor
J
Jordan
Member
Shared resources
📄 launch-brief.pdf
📋 "Write in Acme brand voice…"
💬 12 shared conversations
Team Projects let colleagues share files, instructions, and conversations in one workspace
Team example: A product team creates a "Launch 2026" Team Project with the PRD, brand guide, and messaging doc uploaded. Marketing, design, and engineering each start chats inside it — everyone works from the same context without repeating setup.

When to create a Project

✅
Good fit
  • Ongoing client or account work
  • Writing a book, course, or doc series
  • Repeating tasks with the same reference files
  • Team workflows needing shared context
💬
Regular chat is fine
  • One-off questions
  • Quick code snippets or explanations
  • Brainstorming without reference files
  • Tasks you won't revisit
Summary:
  • Projects group related conversations under one organized workspace.
  • Upload files and set custom instructions once — they apply to every chat in the project.
  • Projects provide persistent context across sessions, unlike regular chats.
  • Team Projects let colleagues share files, instructions, and conversations.

What's Next

Custom Instructions & Personas — set default tone, format, and role without repeating yourself.