CHAPTERS
- 0:00 – 0:15
What Claude Projects are and why they matter
The video defines Projects as self-contained workspaces in Claude with their own chat histories, knowledge bases, and settings. It sets up the main goal: showing what Projects do, how to create one, and which advanced capabilities unlock better workflows.
- •Projects are self-contained environments with separate histories and settings
- •Projects include a dedicated knowledge base and customized configuration
- •The tutorial will cover overview, setup steps, and advanced features
- 0:15 – 0:30
Project knowledge: building a reusable context library
Projects let you upload documents that Claude will automatically consider in every chat within that project. This enables responses that match your organization’s terminology, goals, and background without re-explaining context each time.
- •Upload relevant documents into a project-specific knowledge base
- •Claude automatically uses this knowledge alongside your prompts
- •Improves alignment with team goals, terminology, and context
- 0:30 – 0:45
Handling large information with retrieval (RAG)
For projects with lots of material, Claude can use retrieval-augmented generation to work with more content without hitting typical limits. This expands practical context capacity by retrieving the most relevant pieces for each query.
- •Projects can handle more information than a single chat context window
- •RAG helps Claude pull in relevant context as needed
- •Designed for knowledge-heavy, ongoing workstreams
- 0:45 – 1:00
Project instructions: consistent tone, role, and outcomes
You can define instructions that are applied to every chat in the project, guiding Claude’s tone, perspective, and response style. This is useful for standardizing outputs—for example, formal writing or industry-specific viewpoints.
- •Instructions apply automatically across all project chats
- •Set tone, perspective, expertise level, and desired outcomes
- •Helps standardize outputs for teams and repeatable workflows
- 1:00 – 1:30
Sharing Projects for collaboration (Claude for Work)
On Claude for Work plans, Projects can be shared across an organization to support collaboration and knowledge reuse. The example highlights a brand team creating voice-and-tone guidance for consistent marketing writing.
- •Projects can be shared with coworkers for joint work
- •Enables centralized guidelines and shared knowledge
- •Example: brand voice project used by anyone writing marketing copy
- 1:30 – 2:01
Creating a new Project: name, goal, and management controls
The video walks through creating your first project: click New Project, name it, and describe what you want to achieve. It also points out quick management options like starring, editing details, archiving, or deleting.
- •Create via New Project → name → describe objective → Create Project
- •Use description to clarify goals (example: case study blogs for a flower business)
- •Manage projects with star, edit, archive, and delete options
- 2:01 – 2:31
Visibility settings: private vs team-accessible projects
After creating a project, you choose its visibility—private for personal work or public for team collaboration. Visibility determines who can discover and use the project across your organization.
- •Set project visibility based on collaboration needs
- •Private for individual use; public for broader team access
- •Visibility works alongside instructions and settings
- 2:31 – 3:01
Defining Instructions in detail and saving them for all chats
Inside the Instructions panel, you specify how Claude should respond—tone, response style, expertise level, and goals. Once saved, these instructions apply to every conversation in the project, ensuring consistent outputs.
- •Use Instructions panel to guide Claude’s behavior
- •Specify tone, expertise, response structure, and outcomes
- •Saved instructions automatically apply across all project chats
- 3:01 – 3:32
Adding Files to the project knowledge base (and supported sources)
The Files area is where you upload shared materials that Claude can reference in any project conversation. Supported inputs include PDFs, documents, CSVs, text files, and Google Drive connections.
- •Upload once; Claude can reference files across all project chats
- •Supports PDFs, docs, CSVs, text files, and Google Drive
- •Useful for client materials, guidelines, and reference documents
- 3:32 – 3:48
What is (and isn’t) shared across chats + automatic RAG when near limits
The video clarifies that information isn’t automatically shared between separate chats unless it’s added to the project knowledge base. If the project knowledge approaches context limits, Claude enables RAG to expand usable capacity.
- •Chat content doesn’t automatically transfer between different chats
- •Project knowledge base is the shared, reusable context layer
- •RAG is automatically enabled as knowledge grows toward limits
- 3:48 – 4:04
Starting chats and making them public for teammates
Once the project is ready, you can start chats inside it, and optionally make chats public so others can view and build on them. This supports iterative work where teammates extend prior conversations and outputs.
- •Initiate all work conversations inside the project environment
- •Optionally set chats to public for shared iteration
- •Supports collaborative workflows built on prior work
- 4:04 – 4:34
Permissions model: view, edit, and creator controls
Projects include three permission levels that control access and editing rights. This section explains what each role can do and why choosing the right permissions balances security with collaboration.
- •Can view: read-only project access plus ability to chat
- •Can edit: update instructions, knowledge, members, and contribute content
- •Creator: full control and determines visibility/sharing scope
- 4:34 – 5:05
Collaboration features: Shared With Me, notifications, and multi-member contribution
The video highlights ways teams coordinate in Projects, including a Shared With Me tab and email notifications for newly shared projects. Creators can adjust permissions, while multiple members can add documents and create chats in the same workspace.
- •Shared With Me tab helps users find projects shared by others
- •Email notifications alert users when projects are shared
- •Creators can change permissions or revoke access; teams co-author documents and chats
- 5:05 – 5:35
Uploading files just for a conversation (without adding to project knowledge)
Sometimes you need to reference content temporarily without cluttering the project knowledge base. You can upload files directly in a chat so they remain separate from the project’s shared knowledge.
- •Upload ad-hoc files during a conversation for temporary context
- •Keeps the permanent knowledge base clean and focused
- •Useful for examples, one-off references, or sensitive/temporary materials
- 5:35 – 7:07
Project ideas and wrap-up: examples of how Projects can be used
The video closes with practical examples—product development, content creation, course design, personal finances, and home renovation—to show the flexibility of Projects. It reiterates that customization enables workflows for professional, personal, and team contexts and points viewers to the Help Center.
- •Examples: product development, content creation, education/course building
- •Examples: budgeting/personal finance tracking, home renovation planning
- •Projects help centralize info, generate ideas, and streamline collaboration; see Help Center for more
