Home » Claude Team Admin » How do I control external artifact sharing on Claude Team?

How do I control external artifact sharing on Claude Team?

How do I control external artifact sharing on Claude Team?
Claude Team Admin
Short answer

Claude Team controls outside sharing of artifacts from Organization settings > Artifacts, where External sharing and Email invitations outside your organization are two independent switches. To control artifact sharing outside the company, set both, because turning one off does nothing to the other. External sharing governs artifacts anyone outside your organization can view through a public link. Email invitations govern named outside people your members invite to one artifact. The gotcha: turning External sharing off also stops existing public links from working, except for artifacts an admin allows individually, so check what is already public before you flip it.

Why this matters: What leaves the office when your team works in Claude. This post is the how.

Want sharing rules settled before something leaves the company? Book a short call and I’ll set them up with you.

Before you start

  • Role needed: Owner or Primary Owner. Anthropic’s artifacts guide names those two roles for these settings.
  • Have ready: a short list of artifacts that must stay reachable from outside, such as a client deck or a vendor dashboard, so you can allow them individually.
  • Know the limits: Docs cannot be shared outside your organization yet, and anyone you invite from outside needs a Claude account.
  • How long: about ten minutes, most of it deciding which outside links should survive.
  • What it changes on the bill: nothing. Artifacts count toward existing usage limits and have no separate allowance.

Do this

  1. Click your initials in the lower left, open Organization settings, and click Artifacts under Products in the left menu.

    You’ll see: the Artifacts page, with the Artifacts switch at the top and four indented switches under it: Organization-wide sharing, External sharing, Email invitations outside your organization, and Artifact presence.

  2. Read the External sharing row, then set its switch. Off means nobody outside the organization can view a member’s artifact through a public link.
    Claude Team admin settings, Artifacts sharing block: the outside sharing switches. Callout: External sharing toggle; Email invitations toggle
    Step 2: Artifacts sharing block: the outside sharing switches

    You’ll see: the line “Allow members to publish artifacts that anyone outside your organization can view,” followed by the warning that turning it off stops existing public links from working until you turn it back on, except for artifacts an admin allows individually. In the capture for this guide the switch sat off.

  3. Set Email invitations outside your organization on its own. Leave it on if staff send drafts to named clients or partners; turn it off if nothing should reach an outside inbox.

    You’ll see: the line “Allow members to invite specific people outside your organization to an artifact by email,” and the warning that turning it off also blocks access for people already invited until you turn it back on.

  4. Before you switch External sharing off on an organization that already shares publicly, go to Published artifacts and use Allow external sharing on each artifact on your keep list. Use Manage outside access to review who can still get in.

    You’ll see: the per artifact controls Anthropic’s guide names for this job. Anything you do not allow here goes dark the moment External sharing is off.

  5. Scroll down to Templates and check the Docs row. Docs stay inside the organization no matter how you set the sharing switches.
    Claude Team admin settings, Artifacts Templates block: Slides, Design, Docs, Dashboards and Motion switches
    Step 5: Artifacts Templates block: Slides, Design, Docs, Dashboards and Motion switches

    You’ll see: Slides, Design, Design systems, Docs, Dashboards and Motion, each with its own switch, and the note that turning a template off does not affect artifacts already made from it.

  6. Open Capabilities in the left menu and find Enable artifact connectors under Visuals.
    Claude Team admin settings, Capabilities, Visuals block: artifact connectors and inline visualizations
    Step 6: Capabilities, Visuals block: artifact connectors and inline visualizations

    You’ll see: Enable artifact connectors, described as letting team members work with artifacts that use data from external sources, and Inline visualizations below it. This switch is about data coming in, not about who can view an artifact.

  7. If anyone still works in standalone Claude Design, open Claude Design [standalone] in the left menu and check Allow public links.
    Claude Team admin settings, Claude Design page: Enable for your organization and Allow public links. Callout: Allow public links
    Step 7: Claude Design page: Enable for your organization and Allow public links

    You’ll see: Enable for your organization at the top and the Allow public links switch indented under it, which lets Claude create public links to designs and project files. Standalone Claude Design closes December 14, 2026, so this is a short term check.

What happens next

Which switch controls which outside access

The sharing switches on the Claude Team Artifacts page and what turning each off does, from Anthropic's artifacts admin guide and the settings page, checked 2026-10-25.
Setting What it allows Turning it off Set it off when
External sharing Artifacts anyone outside the organization can view through a public link Existing public links stop working, except artifacts an admin allows individually Nothing your staff build should be public
Email invitations outside your organization Members invite named outside people to one artifact by email People already invited lose access until you turn it back on Client work should never leave by email
Organization-wide sharing Members share an artifact with everyone in the organization Public links also turn off, and organization-wide shares stop working Rarely; this mostly limits internal sharing
Allow external sharing on one published artifact One artifact stays public while External sharing is off That artifact follows the organization setting You need one exception, not a policy change

Michael’s two cents

Anthropic’s guide says External sharing and email invitations are two independent settings, and that turning External sharing off kills existing public links. In a six person office that matters because the owner usually flips one switch, thinks the door is shut, and a client still has an email invitation to last month’s pricing deck. Or the reverse: the owner shuts public links on a Friday and the vendor dashboard everyone relies on goes dark on Monday. I handle it in one sitting. I list what must stay public, allow those few individually, then turn External sharing off. I leave email invitations on for named clients, because each invitation goes to one named person I can see. And I tell staff plainly that Docs stay inside for now.

Michael Robichaud, Strategized.ai

Watch out for

  • The two switches are independent. Turning off External sharing does not stop email invitations, and turning off email invitations does not stop public links.
  • Turning External sharing off breaks every existing public link except the ones an admin allowed individually. Allow the keepers first.
  • Admins cannot restrict which apps artifacts reach. The connectors switch is on or off, not a list.
  • Docs cannot be shared outside your organization yet, so a client who needs to read a document needs another format, such as Slides, which export to PowerPoint or PDF.
  • If your organization is HIPAA ready, Docs, Slides, Design, Dashboards and Motion are not covered by the BAA. Keep regulated data out of artifacts entirely.

If something goes wrong

  • Symptom: a client says a link that worked last week now fails. Fix: External sharing was turned off. Allow that artifact individually under Published artifacts, or turn External sharing back on.
  • Symptom: an outside person cannot open an artifact they were invited to. Fix: check that Email invitations is on, that they have a Claude account, and that the invitation is under 30 days old. Pending invitations expire after that.
  • Symptom: a former employee’s shared artifact is still being asked about. Fix: removing them from the organization ended their artifact access immediately; reshare the work from a current member if it is still needed.
  • Symptom: staff cannot find a way to send a document to a client. Fix: that is expected. Docs cannot be shared outside the organization yet.

What happens to public artifact links when external sharing is turned off?

They stop working until you turn External sharing back on. The only exceptions are artifacts an admin allowed individually.

Can Docs be shared outside a Claude Team organization?

Not yet. Anthropic’s artifacts guide says Docs cannot be shared outside your organization, although the Docs template is on by default on Team for internal use.

How long do outside artifact invitations last?

Pending invitations to people outside your organization expire 30 days after sending. The person also needs a Claude account to open the artifact.

Do artifacts use up extra Claude Team usage?

Artifacts count toward existing usage limits rather than a separate allowance. On Team they draw from each seat’s session and weekly limits, and admins can buy usage credits.

More Claude Team Admin how-tos

Need this done, not just explained?

For a business rolling Claude out to a team, Strategized.ai runs the implementation. For one person setting up a seat or two, CoworkConsultant.com does it on a call.

For a business: Strategized.ai For one person: CoworkConsultant.com

Sources

Anthropic changes these menus. Each source shows the date we checked it.
CoworkStrategy.com is independent and not affiliated with or endorsed by Anthropic. Claude is a trademark of Anthropic, PBC.
Michael Robichaud

Written by

Michael Robichaud

Founder of Strategized.ai and creator of the Claude AI Strategy Stack. Michael sets Claude up for client teams and runs his own five-site content operation on Claude, so what he writes here is tested in real work first.

 ·  Connect on LinkedIn →

Not Sure Where to Start?

Read It

Start with the free guides on this site, then the Learn Claude guides at Strategized.ai when you want the longer walkthroughs.

Learn Claude guides

Install It

The free Foundation Plugin teaches Claude the basics of your work in one download. No application, no card.

Get the free Foundation Plugin

Have It Set Up for You

For your business, Strategized.ai sets Claude up for the whole team. For yourself, CoworkConsultant.com builds your own setup or a custom plugin.

How we help businesses
Just you? See how we help

Two Ways to Get Claude Working for You

Do it yourself with the free guides and plugin, or have it set up for you. Either way you end up in the same place: a Claude workspace configured around the way you work.

Do It Yourself

The free Foundation Plugin, the guides on this site, and the Learn Claude library at Strategized.ai. No application, no card.

Get the free Foundation Plugin

Have It Set Up for You

For your business: Strategized.ai sets Claude up for the whole team, configured for every role, trained on their own work and handed over.

How we help businesses

For yourself: CoworkConsultant.com builds your own Claude setup, or a custom plugin around the job you repeat most.

How we help individuals
The Foundation Plugin: free for business owners and professionals Get it free → Instant download. No account.