CHAPTERS
What Claude Projects are and why they matter
Defines Projects as self-contained workspaces in Claude with their own chat history, knowledge base, and settings. Sets expectations for the video: what Projects are used for, how to create them, and advanced capabilities.
- •Projects are self-contained environments for focused work
- •Each project can have its own chat histories, knowledge, and settings
- •Projects are designed to improve quality and organization of Claude workflows
Project Knowledge: upload documents for automatic context
Explains how project knowledge improves Claude’s responses by letting you upload relevant documents that are automatically considered in every chat within the project. Emphasizes alignment with team terminology, goals, and background.
- •Upload relevant documents into a project knowledge base
- •Claude uses this knowledge automatically alongside prompts
- •Enables more informed, project-specific responses
- •Helps maintain consistent terminology and context across work
Scaling context with automatic retrieval (RAG)
Describes how Projects can handle much more information without hitting typical limits. When a project grows large, Claude uses retrieval-augmented generation to pull in the most relevant context.
- •Projects can support larger information sets than normal chats
- •Claude automatically processes large project knowledge using RAG
- •RAG helps Claude select relevant context when needed
- •Improves response quality on information-heavy projects
Project Instructions: persistent guidance for tone and outputs
Shows how to define project-level instructions that apply to every chat. This is positioned as the place to control tone, perspective, and response style for consistent results.
- •Set project instructions that apply to every chat
- •Use instructions to define tone, expertise level, and style
- •Guide Claude to respond from a specific perspective/industry
- •Instructions complement user preferences and selected style
Sharing and collaboration for Claude for Work teams
Introduces collaboration features available on Claude for Work, including sharing projects with colleagues. Uses a brand-team example to illustrate consistent voice and tone across an organization.
- •Projects can be shared for collaboration on Claude for Work plans
- •Enables knowledge sharing across an organization
- •Example: brand team shares voice/tone guidelines
- •Supports consistent outputs across multiple contributors
Create your first project: name, goal, and project controls
Walks through creating a project in three steps—starting a new project, naming it, and describing the goal. Also points out basic project management controls like starring, editing, archiving, and deleting.
- •Click New Project and assign a name
- •Add a description of what you want to achieve
- •Create the project and access its main page controls
- •Star for quick access; edit details; archive or delete
Visibility settings: private vs team-accessible projects
Explains how to set project visibility depending on whether the project is personal or collaborative. Reinforces that instructions and information should be added to guide chats in the project.
- •Choose Private for personal use or Public for team collaboration
- •Visibility determines who can access the project
- •Project instructions and knowledge shape all chats inside the project
Writing effective Instructions: what to include and why
Goes deeper on the Instructions panel, detailing what you can specify and giving an example for brand guidelines. Notes that saved instructions persist across every chat in the project.
- •Specify tone, expertise level, response style, and desired outcomes
- •Add context about what you’re trying to achieve
- •Example: explain thought process and show brand application
- •Save instructions to apply them to all project chats
Building the knowledge base: adding files and Google Drive content
Covers the Files area where documents added become shared context across all project chats. Lists supported formats and explains how Claude references uploaded materials in responses.
- •Use the Files menu to upload content used across the project
- •Supported: PDFs, documents, CSVs, text files, Google Drive
- •Claude processes files and uses them as chat context
- •Example: upload client brand materials for guideline work
Chat boundaries, RAG auto-enable, and starting project chats
Clarifies that context isn’t shared between separate chats unless it’s added to project knowledge. Notes that when knowledge nears the context limit, Claude automatically enables RAG, and then you can begin chatting within the project.
- •Chat history context doesn’t automatically carry across separate chats
- •Add key info to project knowledge to make it persistent
- •Claude auto-enables RAG as knowledge approaches limits
- •Start new chats inside the project once setup is complete
Making chats public and managing permissions (view/edit/creator)
Explains how teammates can view and build on work via public chats and outlines three permission levels. Emphasizes balancing security with collaboration through the right access controls.
- •Chats can be made public for teammates to view and extend
- •Can view: access contents/knowledge/chat, but no changes
- •Can edit: modify instructions/knowledge/manage members and contribute
- •Creator: full control and decides who can see the project
Team collaboration workflow: discovery, notifications, and co-authoring
Highlights collaboration features like the Shared With Me tab and email notifications when projects are shared. Notes that project creators can adjust permissions, and multiple members can contribute documents and chats in one workspace.
- •Use Shared With Me to find projects others shared
- •Email notifications alert you to newly shared projects
- •Creators can change permissions or revoke access
- •Multiple members can add documents, create chats, and collaborate
Using one-off uploads without cluttering project knowledge
Explains the option to upload content directly in a conversation when you don’t want it added to the project’s knowledge base. Positions this as a clean way to share temporary examples or context.
- •Upload files during a chat to keep them separate from project knowledge
- •Useful for temporary context or examples
- •Prevents cluttering the shared knowledge base
- •Still enables Claude to reference the uploaded content in that conversation
Project ideas and wrap-up: product, content, courses, finances, renovation
Offers example use cases to show Projects’ flexibility across professional and personal work. Concludes with a reminder to customize each project and points viewers to the Help Center for more details.
- •Examples: product development, content creation, course design
- •Examples: personal finance tracking and home renovation planning
- •Projects centralize information and support iterative improvement
- •Customize workflows per project; see Help Center for more guidance
