How to share a Claude artifact, and who can open it
Open the artifact and click Share. On Pro, Max and Ultra you can share it with anyone who has the link or invite people by email. On Team and Enterprise it stays inside your organization unless an Owner allows outside sharing. Free can't share a new artifact. Most people who open a link need no Claude account, and people you invite by email do.
Checked against Anthropic's pages on 16 November 2026.
What each plan can do
| Sharing option | Free | Pro, Max, Ultra | Team | Enterprise |
|---|---|---|---|---|
| Anyone with the link | No | Yes | Only if an Owner turned on External sharing, or allowed that one artifact | Same as Team |
| Everyone in your organization | No | Not applicable | Yes | Yes |
| Specific people in your organization | No | Not applicable | Yes | Yes, and groups |
| Invite by email (beta) | No | Yes | Yes. Invites to outside people are on by default | Yes. Invites to outside people are off by default |
| Publish an older artifact made in a chat | Yes, with "Publish" | Yes, with "Publish" | "Share & copy link" instead | "Share & copy link" instead |
Anthropic's "Share artifacts" table, read 16 November 2026: support.claude.com. "Older" means made in a chat before 16 September 2026. The table shows no sharing option for a new artifact on Free. Everyone starts private: "Artifacts start private to you. Nothing is shared until you share it."
What the person opening it needs
| How you shared it | Claude account to open it? | What works for them |
|---|---|---|
| Anyone with the link | Most artifacts: no. Docs: yes, and view only. Some artifacts show part or all of their content only after sign-in | Parts that use Claude or connected apps don't work from outside your organization or when not signed in, and they can't see or add comments. Saved data can be read once signed in, never changed, and isn't shown to people who aren't signed in |
| Everyone in your organization, or named people in it | Yes, signed in to your organization | Their access level: can view, commenter or can edit |
| Invited by email | Yes, a Claude account with the address you invited | Parts that use Claude or your connectors don't work for outside invitees. An invitation works only for the person you invite |
| Published older artifact | No. Features that use Claude ask them to sign up | Signed-in Free, Pro, Max or Ultra viewers can copy and save it. Their own usage limits apply |
From the same Anthropic page, read 16 November 2026. A connected app inside an artifact uses the viewer's own connection, so a viewer who can't reach that data source sees an error where your data would be.
Steps for each way of sharing
Share by link, with your organization or with named people. Open the artifact and click Share. On Team and Enterprise, add people from your organization and choose each person's access, then under "Who has access" choose "Only people invited", "Anyone at" your organization, or "Anyone with the link". On Pro, Max and Ultra the choices are "Only you" or "Anyone with the link". Copy the link and send it. If "Anyone with the link" is grayed out on Team or Enterprise, an Owner has to allow it.
Invite by email. Click Share and type the person's address in the field at the top. Pick the Invite option that shows their address, choose "Can view", "Commenter" or "Can edit", and click Invite. The invitee has to sign in to Claude with that exact address, creating an account first if they have none. Claude doesn't tell you whether they have one. You can invite up to 50 people from outside your organization per artifact, pending invitations expire after 30 days, and the invitation email is in English. On Team and Enterprise, an address from inside your organization is added directly.
Publish an older artifact. Open it, click Publish and copy the public link. Anthropic's page also describes an embed code with a list of allowed websites. You can't publish an artifact again after you unpublish it.
On a phone. You can't change sharing settings in the Claude apps for iOS or Android. Use Claude on the web or Claude Desktop.
Keeping it private, and taking it back
To stop sharing, open the artifact, click Share, and under "Who has access" choose "Only you" (Pro, Max, Ultra) or "Only people invited" (Team, Enterprise). Removing a person takes their access away right away. One difference matters: if you set it back to "Only you" on Pro, Max or Ultra, people you invited keep their access, and on Team and Enterprise they lose it and their invitations are removed. Deleting the artifact removes everyone.
On Team and Enterprise, two separate Owner switches in Organization settings under Artifacts control sharing outside the organization: External sharing and Email invitations outside your organization. Turning on one doesn't turn on the other. An Owner can also see which artifacts are shared outside and remove people from them. Turning Artifacts off for the organization stops anyone opening, editing, downloading or sharing artifacts, and links stop working until it is turned back on. Nothing is deleted, and older artifacts and live artifacts made in Cowork keep working. Artifacts that connect to other websites can't be shared outside the organization at all.
Saved data and usage
Pro, Max, Ultra, Team and Enterprise artifacts can keep data between visits, private to each person or shared by everyone. Whoever builds the artifact decides which. Anthropic's stated default for a new artifact is up to 100 MB of data and 25,000 saved records, whichever comes first, plus uploaded files of up to 20 MB each (up to 5,000 files and 1 GB in all). Older artifacts keep the earlier limit of 20 MB of text, and unpublishing an older artifact permanently deletes its saved data.
When an artifact calls Claude, the use counts against each viewer's own plan limits and not yours. Anthropic's pages describe no backups, restore, export of saved data or scheduled runs for artifacts (checked 16 November 2026), and no choice of where the data is stored.
Artifacts made in Claude Code
On Pro, Max, Ultra, Team and Enterprise, Claude Code can publish a session's output as an artifact: a page on a private claude.ai address that updates as the session goes on. Each publish becomes a version, and from the Share control you choose which version people see. On Team and Enterprise you can share with named people, everyone in the organization, or a folder. On Pro, Max and Ultra you can also share a public link that anyone can open. On Team and Enterprise that is off until an Owner enables External sharing. People who open a public link see "Content is user-generated and unverified." instead of your name.
An artifact can call connectors each time someone views it, through the account of the person viewing. Those calls don't run for a visitor who opens the public link without signing in, or from outside your organization. Sessions that use an API key or a cloud-provider credential can't publish.
When an artifact stops being enough
Anthropic is plain about it. Its Claude Code documentation says: "An artifact is a capture of work: one self-contained page with no backend, so it can't serve multiple routes. For a hosted internal tool with a backend, deploy it on your own infrastructure instead." A page like that can't sign people in by itself, and it can reach only its own address and a short list of font and script hosts.
In practice there are a few points where people move a tool out of an artifact:
- Colleagues who have no Claude account need to sign in and write data. Outside viewers of a link can read saved data after signing in to Claude, but can't change it.
- The records have to be backed up, and you want to restore yesterday's copy after a mistake.
- The tool should run a job on a schedule with nobody looking at it.
- The data has to sit in a region you choose, or the tool needs an address of your own.
That is when people put the app online with its own sign-in. Haechy is one place to do that: you ask Claude to put the app online, colleagues you add by email get a one-time sign-in link (valid once, for 15 minutes) and need no Haechy or Claude account, the app gets a Postgres database with nightly backups you restore by asking Claude, and you choose US, EU, UK or Australia for the app, its database and its backups. Some services we use to send email, verify phone numbers and take payments process data outside your chosen region. See our sub-processors. The side-by-side is in Haechy or a Claude artifact, the decision guide is the safest way to share an app you built with Claude, and giving colleagues access without accounts covers the sign-in choices. To try it, the quickstart takes a few minutes.
Sources
All read on 16 November 2026. Anthropic changes these pages often, so check them for the latest.
- Share artifacts (sharing options, who can open, invitations)
- What are artifacts and how do I use them? (stored data, files, usage)
- Artifacts admin guide for Team and Enterprise plans (Owner switches)
- Share session output as artifacts (Claude Code)
Haechy is an independent product of DT Global Ventures Ltd. It is not made, sponsored or endorsed by Anthropic. Claude is a trademark of Anthropic, PBC.