Share a Claude Doc or Slides deck outside your organisation.

What launched on 16 September

Anthropic merged Cowork and chat into one Claude and put three document formats into every conversation: Claude Docs, Claude Slides and Claude Design, on what Mike Krieger called a revamped Artifacts platform. Ask for a spec and you get a doc you can co-edit with teammates, comment on, and export to Word, PDF, Markdown or Google Docs. Ask for a deck and you get one you can open, edit, and export as PowerPoint or PDF. Claude Code makes docs and slides as artifacts too, pitched at the team loop: write the spec, share it, then ask Claude to implement it. Rollout is Pro and Max first, over the coming weeks, then Free and Team.

The most-liked ordinary reply under the Claude Code announcement was five words long: the sharing part is what actually matters. It is, and the sharing part stops at the organisation's edge.

The sharing rules, per format

• Claude Docs. Private to you until shared. Team and Enterprise: invite specific people or groups, or everyone in the organisation, as viewers or editors; docs "can't be shared outside your organization yet". Pro and Max: anyone with the link. On every plan, opening a shared doc requires a Claude account. Deleting a doc is permanent, there is no trash, and there is no version history yet.
• Claude Slides. Export as PowerPoint or PDF, per the launch posts. Anthropic has not published a help centre article for Slides at the time of writing, so treat the sharing model as the Docs one until it does.
• Claude Design. Workspace access, or publish as a public artifact. Export as PDF, PPTX, Google Slides or a zip of the project.
• Claude Code. A doc or deck made in a session is an artifact: private to you, then shared with your organisation, or public where an Owner has allowed it. Someone outside the org opening that link gets the not-found screen.

None of the four has a setting for "one person outside the company". A client, a contractor, a board member, a partner agency: the choice is inside-only or public, and public still asks for a Claude account in the case of Docs.

Route one: export to Markdown or HTML, publish

1. Doc: Export, then Markdown. Publish the .md file on Stacktree and it renders as a styled page, headings and tables intact, at a private unguessable link.
2. Deck: ask Claude for the deck as a single self-contained HTML page, one section per slide, keyboard navigation, then publish the file. It opens full-screen in any browser. The deck-as-a-link page has the example and the print stylesheet for the PDF fallback.
3. Design: export the project HTML and publish it; the Claude Design sharing page walks through it.

Whichever you publish, the link opens with no account. Add a passcode or a company email gate if the content warrants one, set an expiry for a review copy, put it on your own domain if it goes out under your name, and when the doc changes, publish the update to the same link rather than sending a new file.

Route two: one sentence from Claude Code

If the doc was made in Claude Code, skip the export. Tell Claude Code to publish the doc to Stacktree and it will, with no account and no key, handing back a private link that opens for anyone you send it to. It can update the same link later. This works because Claude Code can make the request itself; the claude.ai chat cannot, so there you either add the Stacktree connector once, one paste of a URL, or use route one.

Route three: PDF or PowerPoint, for the people who insist

Some procurement processes want an attachment. Export the doc as PDF or Word, the deck as PowerPoint or PDF, and send it. You lose the things a link gives you: knowing it was opened, updating it after sending, and revoking it. So send the link as the primary and keep the file for the person who asks.

Why not a public link

On Pro and Max, "anyone with the link" for a doc still means anyone with a Claude account, which is the wrong ask for a client. For artifacts, a public link is exactly that, public, and a search of claude.ai's public artifact address turns up clinical summaries and policy documents that were plainly meant for a few readers. A private link on your side gets the document to the one person who needs it without either problem.

What to watch

Anthropic's own wording on external sharing for Docs is "yet", so it is on the roadmap. Whether it arrives with account-free viewing, gates, or an expiry is the question that decides how much of this page stays necessary. We will update it when the Slides help article appears, when Docs sharing changes, and when the Free and Team rollout lands. The date at the top is the tell.