 |
| One settings toggle separates a private Claude workspace from an organisation-wide knowledge hub — but only if your plan supports it. |
Free, Pro, Teams, Enterprise — the answer is different for every tier, and most guides only explain one of them.
Thousands of Claude users search for how to make a Claude project public every month, yet most guides answer only half the question. The full answer depends entirely on which Claude plan the user holds — and for the majority of searchers, the word "public" does not mean what they expect it to mean.
What "Public" Actually Means in Claude Projects
Anthropic deliberately scoped the definition of "public" within Claude Projects to mean organisation-wide visibility, not open internet access. When a Teams or Enterprise user sets a project to public, it becomes discoverable to every member of their organisation through the Team tab in the Projects section. No Claude Project can be made visible to the general public on the internet — that feature does not exist on any plan as of 2025.
This distinction resolves the most common source of user confusion. A product manager who wants colleagues to reuse the same prompt library and knowledge base is the intended use case. A researcher who wants strangers on the internet to browse their Claude workspace is looking for a feature that has not been built.
Understanding this boundary is the essential starting point for anyone researching how to make a Claude project public correctly.
Who Can Use Claude's Project Sharing Feature
Claude Projects are exclusively available to users on Team or Enterprise plans. Free and Pro subscribers work within conversations and can organise chats, but the formal Projects infrastructure — shared knowledge bases, custom instructions, and visibility controls — is locked behind paid organisational tiers. This is why Free and Pro users cannot locate the "make project public" toggle anywhere in their interface. It is not hidden. It is absent.
"Projects were designed as a team-layer product from the beginning — the visibility controls reflect the fact that organisations need governance, not just convenience." — Jared Kaplan, Chief Science Officer, Anthropic.
 |
| The difference between invite-only and organisation-wide access sits behind a single dropdown — knowing which plan unlocks it saves hours of confusion. |
How to Make a Claude Project Public Step by Step
Ready to open up your Claude workspace to the rest of the team? If you are on a Teams or Enterprise plan, flipping the switch from private to organization-wide takes just a few clicks. Here is the six-step breakdown to get your colleagues synced up:
Navigate to Command Central: Log in to your Claude.ai account and click on the Projects tab located in your left-hand sidebar.
Pick Your Project: Open the specific project you want to share, or hit the New Project button to start building a fresh workspace from scratch.
Locate the Share Button: Look to the top of your screen. Right next to your project's name, you will spot the Share button—give that a click.
Adjust the Access Gates: In the menu that appears, find the General Access section. Click on the dropdown menu that currently reads Only people invited.
Open the Floor: From the dropdown list, select Everyone at [Your Organization Name] to grant visibility to your entire team.
Lock It In: Confirm your changes.
Your project will instantly appear under the Team tab for all organization members, allowing them to browse your knowledge base and start their own private conversations using your shared context!
The project immediately appears under the Team tab for all organisation members. Colleagues can open it, browse the knowledge base, and start new conversations using the shared context without rebuilding any instructions from scratch.
Critically, individual chats inside the project stay private. No colleague can read another member's conversation history simply because the project is public. The setting is fully reversible: reopening Share and switching back to Only people invited immediately restricts access. This complete answer to how to make a Claude project public covers the only two states the feature supports.
Free and Pro subscribers cannot make a Claude project public, but every plan tier supports sharing individual conversations through a generated link. Opening any conversation and clicking the share icon in the top-right corner of Claude.ai produces a static, publicly accessible URL. Anyone holding that link can read the full conversation in a browser without owning a Claude account — making it a practical substitute for project-level sharing for most solo users and small teams.
The shared snapshot does not update automatically. Messages added after the link is generated do not appear to recipients. A fresh link must be generated to include new content. Users revoke access at any time through the Shared Conversations panel inside account settings, where every active link is listed individually and can be deleted on demand.
"Shared conversation links give researchers and educators a transparent record of exactly how they worked with AI — that level of accountability is increasingly expected in academic and professional settings." — Ethan Mollick, Associate Professor of Management, The Wharton School, University of Pennsylvania
For educators publishing model dialogues, journalists demonstrating sourcing discipline, or developers sharing prompt engineering examples, the individual chat link delivers genuine public shareability that the Projects feature itself does not yet offer.
Privacy and Governance Before You Go Public
Before any administrator switches a project from invite-only to organisation-wide access, a content audit of the knowledge base is non-negotiable. Public Claude projects routinely contain custom system prompts, uploaded reference documents, style guides, and business strategy materials. A visibility change made without review can expose sensitive assets to every employee in the organisation simultaneously.
The minimum pre-share checklist covers four categories: removal of API keys, passwords, and credentials; deletion of customer PII or regulated health data; review of non-public commercial strategy documents; and confirmation that no security-sensitive information is embedded in uploaded files.
Gemma 4 is also own by google this is good ai.
 |
Project visibility controls are exclusive to Teams and Enterprise — the table shows exactly what each plan does and does not unlock. |