A Claude project can hold knowledge files, project instructions, and a series of related chats. When someone asks, "Can I share a Claude project?", they may mean one of two things: invite another person into that workspace, or send them something the project produced.
Those jobs have different answers. The full project can be shared only with members of the same Team or Enterprise organization. On Free, Pro, and Max, you can share eligible chat snapshots or publish artifacts instead. On Team and Enterprise, those native chat and artifact links also stay inside the organization, so external delivery requires an export.
HummingDeck is our product. I will distinguish Claude's native options from the tracked-file workflow, including when the native option is enough.
Can you share a Claude project? The short answer
Projects are available on every Claude plan, and Free users can create up to five. Native project sharing is different: Anthropic documents it only for Team and Enterprise members in the same organization.
| What you share | Availability | Who can open it | Main tradeoff |
|---|---|---|---|
| Full Claude project | Team and Enterprise | Members of the same organization with access | Ongoing workspace, but no external guest or public project link |
| Chat snapshot | Free, Pro, Max, Team, Enterprise | Anyone with the link on personal plans; same-org members on Team and Enterprise | Shows the conversation, including your prompts |
| Published or shared artifact | Free, Pro, Max, Team, Enterprise | Public on personal plans; authenticated same-org members on Team and Enterprise | Shares the output without the full workspace |
| Downloaded or exported file | Any plan that can create the output | Whoever the external host permits | Access and analytics depend on the hosting service |
The key distinction is workspace versus output. If another person needs the same knowledge and instructions for ongoing work, share the project inside an organization. If they only need the result, share a chat, publish an artifact, or export a file.
How to share a full project inside Team or Enterprise
Anthropic's project visibility and sharing guide gives the current flow:
- Open the project and click Share beside the project name.
- Choose Everyone at your organization for organization-wide access, or Only people invited for a private project.
- For a private project, add members by name or email. You can paste multiple email addresses at once.
- Choose view/use access or Can edit. View/use access lets a member see the project's knowledge and instructions and start chats. Edit access also lets them change the knowledge, instructions, and member settings.
Public means public to your organization
Claude calls the organization-wide setting Public. It does not create a public web link. An organization owner can also disable organization-wide projects while leaving private member invitations available.
Your chats remain private when you share a project. Other members can use the same knowledge and instructions, but they do not see your conversations unless you share those chats separately. Archiving a shared project resets its permissions to private and removes the previous sharing context.
What people outside your organization can receive
Claude does not document an external guest role for projects. To access the workspace itself, a recipient must become a member of the organization in an available seat, subject to its domain and admin policies. For everyone else, share one of these three output layers.
1. A chat snapshot
On Free, Pro, and Max, use the chat's Share button to create a snapshot that anyone with the link can view. Team and Enterprise chat links work only for members of the same organization. The snapshot includes messages sent before sharing and eligible artifacts; later messages stay private unless you refresh the snapshot.
There are privacy limits worth checking in Anthropic's chat-sharing guide: uploaded attachments and raw MCP tool data are excluded. Anthropic also disables public sharing for conversations containing file artifacts created through code execution. Review the snapshot before sending it.
2. A published artifact
Free, Pro, and Max users can publish an artifact to a public link. Anyone with the URL can view and use its basic functionality without a Claude account; signing in is required to customize it or use AI-powered features. You can later unpublish it, but Anthropic does not document recipient-specific permissions or engagement analytics for public artifacts.
On Team and Enterprise, artifacts cannot be published publicly. They can only be shared within the organization, viewers must authenticate, and an artifact created from a project also requires access to that project. Anthropic documents the full plan split in Publish and share artifacts.
3. A downloaded or exported file
The artifact panel includes a download action, so you can take the output out of Claude and share it through another service. Test the downloaded file before sending it because the format and behavior depend on the artifact.
Claude Design has a more explicit export menu with ZIP, PDF, PPTX, and standalone HTML. If that is the product you are using, follow the dedicated Claude Design external-sharing guide.
How to recreate a project for another user
Claude does not document a way to transfer one project to another person's account or import it into another personal account. The practical handoff is to send the source knowledge files, copy the project instructions, and create a new project on the recipient's account. Share any eligible chats they need as snapshots.
This recreates the core setup, but the two projects do not stay in sync and chat history cannot be imported. Anthropic confirms that a Claude data export cannot be imported into another personal account. The separate exception is a one-way migration of an entire personal account, including its projects, into a Team or Enterprise organization.
How to share an exported deliverable with HummingDeck
Use this route when a client, investor, or contractor needs the deliverable without seeing the project or your prompts.
- Download or export the output. Use the artifact download control, ask Claude to create a PDF, PowerPoint, Word, or Excel file, or export Claude Design as standalone HTML. Open the file locally and test it first.
- Upload it to HummingDeck. HTML runs in a sandboxed viewer; PDF, PPTX, DOCX, and spreadsheet files use their corresponding viewers. There is no Claude account connection or import permission to grant.
- Create the share link. The Free plan covers five documents, five links per document, real-time view notifications, unlimited viewers, and whole-link revocation. Starter adds per-page analytics, click tracking, and expiration. Pro adds a verified email allowlist plus stakeholder and viewer-network views. Business adds custom domains. Check the current plan comparison before choosing a control.
- Send the link and read the signal. Paid analytics can show time per page, completion, clicks, and return visits. A new unique viewer on the same link can be a likely-forward signal, not proof of who shared it.
Restricted Access uses a one-time verification link sent to each allowlisted email address. It does not use a code, and it ties access to control of that inbox rather than proving a person's real-world identity.
For a broader comparison of public hosts, developer platforms, and tracked-sharing tools, see Host a single HTML file: 8 tools compared.
Which sharing option should you use?
- A teammate needs the same context for ongoing work: share the full project inside Team or Enterprise.
- Someone needs to see your reasoning and prompts: share an eligible chat snapshot.
- You want a public interactive output from a personal plan: publish the artifact.
- An external recipient needs a private deliverable or engagement tracking: export the file and use a controlled share link.
- Another Claude user needs their own editable setup: recreate the project from the source files and instructions.
FAQ
Can I share a Claude project with someone outside my organization?
Share the output rather than the workspace. Personal-plan users can send an eligible chat snapshot or publish an artifact; users on any plan can download or export a deliverable and host it elsewhere. The full project can only be shared with members of the same Team or Enterprise organization.
Can Free, Pro, or Max users share a Claude project?
Free, Pro, and Max users cannot invite another person into the project workspace. They can share eligible chat snapshots, publish artifacts, or export files. Free users can create up to five projects.
Are my chats visible when I share a Claude project?
Your chats stay private by default. Project members share access to the knowledge and instructions and start their own chats; they see one of your conversations only when you share that chat separately.
Can someone view Claude project work without a Claude account?
Public artifacts published from Free, Pro, or Max support basic viewing without a Claude account. Exported files hosted elsewhere also require no Claude account, though the host may impose its own access check. Team and Enterprise artifact links require authentication in the same organization.
What is the difference between sharing a project and sharing a chat?
A shared project is an ongoing workspace with common knowledge and instructions. A shared chat is a snapshot of one conversation. Project sharing is for same-organization collaboration; chat sharing is for showing the reasoning or result of a specific exchange.
Can I transfer or copy a Claude project to another user?
Recreate the core setup by sending the source knowledge files and copying the project instructions into a new project. Claude does not document a single-project transfer or personal-account import, and the copies will not stay synchronized. An entire personal account can be migrated one way into a Team or Enterprise organization.
Share the right layer
The honest answer to "Can I share a Claude project?" is yes inside a Team or Enterprise organization. Outside it, share the smallest layer the recipient needs: the conversation, the artifact, the file, or a recreated setup.
Related:
- How to share Claude Design outside your Anthropic organization: the detailed standalone HTML and PDF export workflow for Claude Design.
- Host a single HTML file: 8 tools compared: public, developer, and tracked hosting options for exported HTML.
- How to add analytics to an HTML page: five tracking approaches, from scripts to per-recipient links.
- AI deck tools for sales and fundraising in 2026: where Claude Design fits among current presentation makers.
- Why your deck analytics are wrong: how bots and security scanners distort document engagement.