# How to share a Claude Doc or Claude Slides deck outside your organisation · Stacktree Source: https://stacktr.ee/blog/share-claude-docs-slides-outside-organization [Skip to content](#main) [stacktr.ee](/) [Examples](/#proof) [How it works](/#how) [Pricing](/pricing) [Security](/security) [Log in](https://app.stacktr.ee) [Publish one](https://app.stacktr.ee/?join=1) By [Steve Smith](/about) · Founder, Stacktree Last updated September 17, 2026 blog · living status · 17 September 2026 # Share a Claude Doc or Slides deck outside your organisation. Claude Docs, Claude Slides and Claude Design arrived in every conversation on 16 September, and in Claude Code. Co-editing, comments, export to Office. What they do not do is reach anyone outside your Claude organisation: Docs cannot be shared externally on Team and Enterprise, and every shared doc needs a Claude account to open. Here is the sharing model as Anthropic documents it, and the routes that get the work to a client anyway. [ Get started free ](https://app.stacktr.ee/?join=1&from=seo_blog_share_claude_docs_slides_outside_organization) install npx stacktree-install Copy No card · 3 pages free · about a minute ## Can you share a Claude Doc outside your organisation? Not on Team or Enterprise plans, where docs can only be shared with people or groups inside the organisation. On Pro and Max a doc can be shared with anyone who has the link, but opening it requires a Claude account. To reach a client, contractor or board without an account, export the doc as Markdown or a deck as HTML and publish it as a private link. ## On this page - 01 [ What launched on 16 September ](#launched) - 02 [ The sharing rules, per format ](#rules) - 03 [ Route one: export to Markdown or HTML, publish ](#export) - 04 [ Route two: one sentence from Claude Code ](#claude-code) - 05 [ Route three: PDF or PowerPoint, for the people who insist ](#pdf) - 06 [ Why not a public link ](#public) - 07 [ What to watch ](#watch) ## 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](/blog/claude-artifact-page-not-found). 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 - 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. - 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](/send-deck-as-link) has the example and the print stylesheet for the PDF fallback. - Design: export the project HTML and publish it; the [Claude Design sharing page](/share-claude-designs) 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. Fix it now You've read why the public link is a problem. Paste the artifact here and get a private one, no account, and a passcode if you want it. Paste HTMLDrop a fileno account · 24 h linkHTML to publishAdd a passwordPublish private link The doc, on a link the client can open Publish the Markdown export or the HTML deck and send one private link. No Claude account to open it, a passcode if you want one, updated in place when the doc changes. Three pages free, no card. [ Publish the export → ](https://app.stacktr.ee/?from=blog_cta_share_claude_docs_slides_outside_organization&join=1) Free to try: 3 pages, each live for 7 days. Own domain from $19/mo. FAQ ## Frequent questions Can I share a Claude Doc with someone outside my organisation? + Not on Team or Enterprise plans. Anthropic's help centre says docs "can't be shared outside your organization yet"; you can invite people or groups inside it, or everyone in it. On Pro and Max you can share with anyone who has the link, but opening a shared doc still requires a Claude account. For an outside reader, export the doc and publish the export. Does a client need a Claude account to open a shared Claude Doc? + Yes, on every plan. The help centre states it directly: opening a shared doc requires a Claude account. A client, contractor or board member without one sees a sign-in wall or a not-found page. A published export on a private link opens in any browser with no account. What formats can I export a Claude Doc to? + Word (.docx), PDF, Markdown (.md) and Google Docs, from the Export button on the doc. Editors can export; viewers cannot. Markdown is the one to pick when the destination is a web page, since it carries the headings and tables and publishes as a styled page in one step. How do I share a Claude Slides deck with a client? + Export it as PowerPoint or PDF and send the file, or ask Claude for the same deck as a single self-contained HTML page with one section per slide and publish that as a private link. The page version opens full-screen in any browser, needs no account, can carry a passcode, and updates in place when the deck changes. Can Claude Code publish a doc or deck somewhere other than claude.ai? + Yes. Claude Code makes docs and slides as artifacts, which share within your organisation. Tell it to publish the doc to Stacktree instead and it will, with no account or key, returning a private link that opens for anyone you send it to. The claude.ai chat cannot do this on its own; there you add the Stacktree connector first, or export. Why does a Claude Doc link stop working for someone? + Three reasons: the doc was shared inside an organisation they are not in, the doc was deleted, which is permanent with no trash, or they are not signed into a Claude account at all. A published export on your own link is not subject to any of the three. Keep reading ## Related guides - [ Send a deck as a link, not a 40MB attachment The HTML deck pattern with the example board deck and the print-to-PDF fallback. ](/send-deck-as-link) - [ How to share a Claude Design outside your workspace Export the project HTML, publish it privately. ](/share-claude-designs) - [ Claude artifact "Page not found" What the person outside your organisation sees, and what to ask the sender for. ](/blog/claude-artifact-page-not-found) - [ Claude artifacts public sharing: what it can and cannot do The sharing matrix by surface and plan, now with the Docs rows. ](/blog/claude-artifacts-public-sharing) - [ Clients view without an account Why the link should be the credential when the reader is outside the company. ](/client-view-without-account) References ## Sources and further reading - [ Get started with Claude Docs (Claude Help Center) ↗ Plans, the sharing rules by plan, the Claude-account requirement, export formats, and the known limitations. ](https://support.claude.com/en/articles/16923645-get-started-with-claude-docs) - [ Get started with Claude Design (Claude Help Center) ↗ Workspace or public-artifact sharing, and the export formats. ](https://support.claude.com/en/articles/14604416-get-started-with-claude-design) - [ Claude Code can now make docs and slides as artifacts (Thariq, Claude Code, 16 September 2026) ↗ The Claude Code half of the launch, and the replies about sharing. ](https://x.com/trq212/status/2100270818433643000) - [ Claude Docs, Slides and Design in every conversation (Mike Krieger, 16 September 2026) ↗ The announcement of the revamped Artifacts platform. ](https://x.com/mikeyk/status/2100260130529161272) ## Inside the org, Claude. Outside it, a link. A private page per deliverable, opened with no account, gated when it needs to be, on your domain when it goes onward. [ Sign up free → ](https://app.stacktr.ee/?join=1&from=cta_blog_share_claude_docs_slides_outside_organization) install npx stacktree-install Copy stacktr.ee [About](/about) [Blog](/blog) [Changelog](/changelog) [Pricing](/pricing) [Security](/security) [FAQ](/faq) [Made with Stacktree](/made-with) Building with AI agents? See the [developer docs →](/developers) --- Full markdown summary of the Stacktree marketing surface: https://stacktr.ee/llms-full.txt