Essay/Claude·Apr 12, 2026

Claude Projects and Workspaces: Setup Guide for Teams

Claude Projects and Workspaces explained: how to organize context, files, custom instructions, clients, departments, and recurring workflows without mixing them.

Luke Thompson
Luke ThompsonApr 12, 2026 · 3 min read
In this article
Claude Projects and Workspaces: Setup Guide for Teams
Claude Projects and Workspaces solve the same problem from different levels. Projects hold the context for one initiative. Workspaces keep related projects organized so teams do not mix clients, departments, or operating modes.

Short answer: Projects vs Workspaces

Use a Project for a specific client, product, or recurring deliverable. Use a Workspace to group related projects, such as all active client accounts, all marketing work, or all internal operations systems.

Workspace setup checklist

Why This Matters

Projects are powerful, but they become chaotic at scale. Imagine you have:

  • 20 projects for your startup
  • 15 projects for side projects
  • 10 projects for learning new technologies
  • 5 projects for personal tasks

That's 50 projects in a flat list. Good luck finding anything.

Workspaces add hierarchy. Now you can create:

  • A "Startup" workspace with company projects
  • A "Side Projects" workspace for experiments
  • A "Learning" workspace for courses and tutorials
  • A "Personal" workspace for home tasks

Switch workspaces with one click, and Claude's context adapts.

Shared Context Across Projects

The killer feature: workspace-level knowledge bases.

Related essay
Claude Projects Explained: Organize Work & Multi-File Context

Upload documents, code repositories, or API documentation at the workspace level, and every project in that workspace can access it.

  • Product requirements document
  • API documentation
  • Brand guidelines
  • Code style guide

Now every project in that workspace ("Landing Page," "Dashboard UI," "API Integration") has access to those documents without re-uploading them.

Workspace Settings

Each workspace gets independent configuration:

Related essay
Every Claude Product Compared: Which One Should You Use?

Set your default model per workspace. Use Opus 4 for work projects, Sonnet 3.7 for quick tasks.

Give Claude workspace-specific context: "In this workspace, always write React components using TypeScript and Tailwind."

Connect different tools per workspace. Your work workspace connects to Linear and GitHub, your personal workspace connects to Notion and Google Calendar.

Workspaces have their own sharing settings. Share your "Work" workspace with teammates but keep your "Personal" workspace private.

Migration and Limits

All your current projects live in a default "General" workspace. Create new workspaces and drag projects to organize them.

Read the original source on anthropic.com

  • Free tier: 3 workspaces, 10 projects per workspace
  • Claude Pro: Unlimited workspaces, 100 projects per workspace
  • Claude Team: Unlimited everything, workspace sharing with team

Quick Takeaway

Workspaces turn Claude Projects from a flat list into a hierarchical organization system. If you use Projects heavily, create workspaces today - you'll immediately feel more organized.

The shared knowledge base feature is especially powerful. Stop uploading the same documents to every project and start using workspace-level context instead.

Field note

Claude API Reference: Official API documentation for Claude integration Learn more

THE CLAUDE INSIDER

Get the Claude playbook in your inbox.

One weekly email for Claude and Claude Code users. Real workflows, no hype. Subscribe and we send you The Claude Power-User Cheatsheet.

GUIDES AND COMPARISONS

— ¶ —

Luke Thompson

Luke Thompson

Editor-in-Chief · The Claude Insider

Luke Thompson is the founder of The Operations Guide, LLC and editor of The Claude Insider. Based in Jonesborough, Tennessee, he has spent years building AI-augmented business systems and automation workflows for operators and teams. He began working with large language models in production well before the current wave of consumer AI tools, integrating them into client workflows, content pipelines, and operational infrastructure. At The Claude Insider, he writes about Claude with the specificity of someone who uses it daily as a professional tool — not as a reviewer or commentator, but as a builder. His coverage focuses on what actually works: prompt patterns, API integration strategies, agentic workflows, and the real-world tradeoffs that practitioners face. He is not affiliated with Anthropic, PBC.

Articles are researched and drafted with AI assistance, reviewed and edited by Luke Thompson.

From Reading to Action

Know where AI can pay off in your company.

Take the free two-minute AI Readiness Assessment. See your score, the two gaps holding you back, and the next move worth making.

Get your readiness score

Instant report · No account to start

Related reading

View archive →