How to make a Claude project public: step-by-step guide for Teams and Enterprise

AI tools 7 min read

Claude projects can't be made public on the web. Learn how to share a project with your organization on a Team or Enterprise plan, and share artifacts.

By Khubaib Riasat
Founder and CEO, AmazeTech

On this page
  1. What “public” actually means in Claude projects
  2. Prerequisites: what you need before making a Claude project public
  3. How to make a Claude project public (step-by-step)
  4. What happens after you make a Claude project public?
  5. How to share a single conversation within a project
  6. How to publish and share Claude Artifacts
  7. How to change a Claude project back to private
  8. How to share Claude projects with external users
  9. Permission levels explained
  10. Common mistakes when making Claude projects public
  11. FAQs

Learning how to make a Claude project public is becoming increasingly important as teams adopt Anthropic tools for collaborative AI workflows. But there is one critical detail many users misunderstand: a Claude project public setting does not mean your project becomes visible on the open internet.

Instead, Claude project visibility is primarily designed for organization-wide sharing on Claude’s Team and Enterprise plans. Understanding the difference between project sharing, conversation sharing, and artifact publishing is essential before changing any access settings.

This guide explains how to share a Claude project, what each permission level does, how artifact sharing works, and how to manage project visibility. Checked against Anthropic’s Help Center on November 9, 2026.

What “public” actually means in Claude projects

Before you share a Claude project, you need to understand what “public” means inside the Claude ecosystem.

Public = visible to your organization, NOT the open internet

In most cases, a Claude project public setting means the project becomes visible to members of your organization only. This applies to:

  • Claude Teams
  • Claude Enterprise

When you enable Claude project public visibility, everyone in your organization can view and use the project, where administrators have enabled it.

It does not automatically create a public internet URL.

Individual chats stay private by default even in a public project

A common misconception about sharing a Claude project is assuming every conversation becomes visible automatically.

That is not how Claude Projects work.

Even if a project is shared organization-wide:

  • Individual chats usually remain private by default
  • Conversations may still require explicit sharing
  • Sensitive discussions should still be reviewed before enabling broader access

This separation helps teams collaborate while protecting confidential conversations.

Project public vs Artifact public: two different things

Another important distinction:

Claude project public

  • Shares the workspace internally
  • Gives collaborators access to the project knowledge base
  • Enables org-wide visibility

Claude Artifact public

  • Creates a shareable public URL
  • Can be embedded on websites
  • May be accessible outside your organization

Artifacts are separate from the Claude project public system.

Prerequisites: what you need before making a Claude project public

Not every Claude account supports public project sharing.

Plan requirement: Team or Enterprise Plan only

The ability to make Claude project public is generally limited to:

  • Claude Teams
  • Claude Enterprise

Users on:

  • Claude Free
  • Claude Pro
  • Claude Max

can publish artifacts publicly, but they typically cannot enable organization-wide Claude project visibility.

Organization setting: admins control project sharing

In many Enterprise environments, admins control whether users can make Claude project public.

Organization administrators may:

  • Allow all public projects
  • Restrict sharing permissions
  • Disable organization-wide visibility entirely
  • Limit external sharing

If the “Share with your broader organization” option is missing, your admin settings may block it.

Content review before expanding access

Before changing Claude project visibility:

  • Remove confidential information
  • Review uploaded files
  • Check embedded prompts
  • Audit the project knowledge base
  • Verify collaborator permissions

Remember that Can Edit users may access the entire project context.

How to make a Claude project public (step-by-step)

Here is how to share a Claude project on a Team or Enterprise plan.

Step 1: Open the Project in Claude.ai

Go to:

Claude.ai

Open the specific project you want to share.

Step 2: Click the Share Button

Inside the project interface:

  • Locate the Share button
  • It usually appears in the top-right corner
  • Open the sharing panel

This is where Claude project visibility settings are managed.

Step 3: Under General Access, Click “Only People Invited”

By default, most projects are private.

You will typically see:

Only people invited

This means only manually added collaborators can access the project.

Step 4: Change to “Everyone at Your Organization”

To make Claude project public internally:

  • Open the dropdown
  • Select:
    Everyone at [Your Organization]

This enables organization-wide visibility.

Step 5: Confirm the Change

After confirmation:

  • The project appears in the Team tab
  • Authorized members can discover it
  • Shared knowledge base access becomes available
  • Team collaboration becomes easier

Your project is now shared.

What happens after you make a Claude project public?

Once a Claude project public setting is enabled:

  • Team members can locate the project
  • Collaborators may request access
  • Shared prompts and context become reusable
  • Project discoverability increases across the organization

However:

  • Private chats may remain private
  • Artifact publishing is still separate
  • External internet visibility is not automatic

How to share a single conversation within a project

Sometimes you do not want the entire project visible.

Instead, you may want to share one conversation.

Open the specific chat

Navigate to the conversation inside the project.

Click share

Claude may provide options such as:

  • Create shareable link
  • Internal organization access
  • Keep private

Choose the visibility level you need.

A public link may allow:

  • Read-only viewing
  • External access
  • Browser-based sharing

But organization-wide project sharing and conversation sharing are separate systems.

How to publish and share Claude Artifacts

Artifacts are one of the most useful features in the Claude ecosystem.

Publishing an Artifact

Artifacts can include:

  • Documents
  • Charts
  • Diagrams
  • Code outputs
  • Interactive content

After generating an artifact:

  • Click Publish
  • Generate a public URL
  • Enable sharing

Artifact publishing is available even on some non-Team plans.

Getting the public URL

Once published, Claude generates:

  • A shareable public link
  • Optional embed support
  • External viewing access

This is the true internet-facing sharing mechanism.

Getting the embed code

Embed code is available only for published legacy chat artifacts on Free, Pro, Max and Ultra: after publishing, click “Get embed code” and list the allowed sites.

You can:

  • Copy the HTML snippet
  • Embed it into websites
  • Add it to CMS platforms
  • Share interactive outputs publicly

How to change a Claude project back to private

If you need to reverse the process:

Public to Private Steps

  1. Open the project
  2. Click Share
  3. Open General access
  4. Change:
    • Everyone at organization
      to
    • Only people invited
  5. Save changes

This immediately reduces Claude project visibility.

How to share Claude projects with external users

A standard Claude project public setting does not usually support open internet access for full projects.

Instead, use these workarounds.

Publish Individual Artifacts

Artifacts are the best external sharing option.

They provide:

  • Public URLs
  • Easy browser access
  • Embed support

Export Chat Transcripts

You can export:

  • Conversations
  • Research summaries
  • Documentation
  • AI-generated outputs

Then share them manually as PDFs or documents.

Claude Code Export + GitHub

For developers using Claude Code:

  • Use the /export command
  • Push outputs to GitHub
  • Deploy demos on Vercel or GitHub Pages

This is common for technical collaboration.

Permission levels explained

Understanding permissions is critical when sharing a Claude project.

Can View

Users can:

  • Read project content
  • Access shared context
  • Review outputs

But they typically cannot:

  • Modify files
  • Edit prompts
  • Change project settings

Can Edit

Users with edit access can:

  • Modify prompts
  • Add files
  • Change project knowledge base
  • Edit shared instructions

Use this carefully.

Admin Controls

Organization admins can:

  • Disable public projects
  • Restrict sharing
  • Limit external access
  • Enforce compliance rules

Enterprise environments often centralize these permissions.

Common mistakes when making Claude projects public

Common errors include:

  • Confusing public with internet-visible
  • Forgetting private chats still exist
  • Sharing sensitive knowledge bases
  • Giving edit access too broadly
  • Publishing artifacts unintentionally
  • Assuming all plans support public sharing

Always review permissions before enabling broader access.

Final thoughts

Sharing a Claude project is mostly about understanding Claude’s collaboration architecture.

The key takeaway is simple:

  • Projects are usually shared internally
  • Conversations can remain private
  • Artifacts are the primary public-sharing mechanism
  • Teams and Enterprise plans open up the full collaboration workflow

Once configured correctly, Claude Projects become a powerful system for collaborative AI research, documentation, SEO workflows, development, and internal knowledge management.

FAQs

  1. Can I make a Claude project public on the free plan?

No. Projects can be shared only on Team and Enterprise plans, and only with people in your organization. Free accounts can create up to five projects but cannot share them. On Pro, Max and Ultra you can share individual artifacts by link instead.

  1. Does making a Claude project public make it visible on Google?

No. A Claude project public setting usually means visibility inside your organization only, not public indexing on the internet.

  1. What is the difference between a project and an artifact in Claude?

A project is a collaborative workspace with shared context and knowledge bases. An artifact is an individual output, such as a document or chart, that can be published with a public URL.

  1. Can external users access my Claude project?

Not directly in most cases. External sharing is usually done through:

  • Published artifacts
  • Exported documents
  • Shared conversation links
  • GitHub or Vercel deployments
  1. How do I change a Claude project from public back to private?

Open the project, click Share, go to General access, and switch from “Everyone at your organization” back to “Only people invited.”

Need help implementing AI collaboration systems, SEO automation, or custom AI workflows for your business? Explore AmazeTech for AI-powered development, automation, and scalable digital solutions.

Read enough? Get a plan for your site.

Free website growth audit. We check your site speed, your Google Business Profile and how calls and forms are tracked, then email you what to fix first. You approve a written plan before work starts.

Book a Growth Call

Certified partners and accreditation

  • Google PartnerGoogle Ads
  • Meta PartnerFacebook and Instagram
  • HubSpot PartnerSolutions Partner
  • Shopify PartnerStores and themes
  • BBB Accredited Business
Free website growth audit

Get your free website growth audit.

Send us your website. A strategist scores it out of 100 on speed, Google Maps, search and lead tracking, then emails you the three fixes that would bring the most calls and bookings. Within 48 hours.

Enter your website, like yourbusiness.com.
Enter a work email so we can send the audit.
Free. No call needed, no newsletter.