Share a Claude Artifact and check who can use it
You send a colleague the checklist Artifact you built this morning. It works perfectly for you. For them, the top half shows an error.
What you'll make
a checked share decision for one Artifact and a short handover note, with the recipient’s view confirmed rather than assumed.
What you'll need
Claude on the web or desktop (sharing settings can’t be changed in the mobile apps), an Artifact you’re allowed to share, the person or group it’s for, and about ten minutes plus a quick check with the recipient.
Example result.
Artifact: New starter first-week checklist (5 items, tick boxes)
Shared with: Anyone at [organisation] — Can view
Recipient check: Priya opened it in her own account; all 5 items visible; ticking item 1 worked.
Not included: calendar panel removed (it used the viewer's own calendar connection).Sharing makes an Artifact available under the conditions you pick. It doesn’t give the recipient your connections or automatically grant editing rights. Check which content and files the sharing route exposes; a successful view in your account is only your account’s view.
1. Check the whole Artifact before you share it
Read the visible content, any downloads and anything the Artifact stores. Check it stands alone without exposing unrelated work from the conversation.
Legacy chat Artifacts on Team and Enterprise: sharing with Share & copy link also gives viewers access to the attachments and files in the originating chat. Check every file for sensitive information before sharing.
Two behaviours matter most. A connected Artifact uses the viewer’s connections, not yours, so a section that reads your calendar will show an error for someone without the same access. And some Artifacts save information that everyone who opens them can see, so don’t type anything sensitive into one before sharing.
List what this Artifact contains: its visible sections, any downloads, any information it stores that other viewers could see, and any connected app or source it reads from. Say which sections would behave differently for a viewer without my connections. Do not change sharing settings.Claude can list what’s in the Artifact and which connectors it calls. It can’t see who has access; you check that in Share.
Why this works: knowing which parts depend on your connections tells you in advance what will break for someone else.
What you should see: a short list of sections, stored data and connections, with the ones that depend on the viewer marked.
2. Choose the narrowest audience and access level
Open the Artifact and select Share (for an Artifact in a chat, it’s in the upper right corner of the Artifact). The options depend on your plan:
| Plan | Who has access | Access level |
|---|---|---|
| Pro and Max | Only you or Anyone with the link; email invitations in beta | Can view, Commenter or Can edit (some types offer only view or edit) |
| Team and Enterprise | Only people invited, Anyone at [your organisation] or Anyone with the link | As above |
For one colleague in the same organisation, invite them, or choose Anyone at [your organisation] with Can view if they only need to use it. On Team and Enterprise, Artifacts stay inside the organisation by default; Anyone with the link needs an owner to turn on external sharing. Don’t choose “Anyone with the link” just because a narrower option takes more thought.
Why this works: the narrowest option that does the job is the one you won’t have to undo later.
What you should see: the audience and access level you meant, shown in the Share dialog before you copy the link.
3. Check the recipient’s experience
Ask the recipient to open it in their own account and tell you what they see. Recipients generally need a Claude account. Don’t borrow anyone’s sign-in to check. Confirm three things: it opens, the intended content is visible, and the one interaction they need (ticking an item, changing an input) works.
Why this works: only the recipient’s account can show the recipient’s view.
What you should see: a short confirmation from the recipient, naming the content and the interaction they tested.
Check the result
- The Share dialog shows the audience and access level you meant.
- The recipient opened it in their own account and the content matched.
- The one interaction they need works for them.
- Nothing sensitive sits in the Artifact’s stored information.
The usual failure: a section that depends on your connections or data fails for the recipient: an error where your calendar appeared, or a Save button that does nothing. The tempting fix, copying your private data into the Artifact, makes it visible to everyone. Spot it by asking the recipient which sections show errors.
The recipient sees [failure]. Keep the same audience and access. Revise the Artifact so that section works without my connections, using only [permitted content], or tell me if an export in [format] would meet the need instead. Do not copy my connected data into the Artifact's stored information.[failure] is what they saw; [permitted content] is what may go in; [format] is an alternative such as a PDF.
Worked example: your calendar isn’t the colleague’s calendar
Fictional example. A team lead builds a first-week checklist Artifact for new starters:
1. Collect your laptop from the IT desk (Monday, 09:30)
2. Book a fire-safety briefing
3. Read the expenses policy
4. Meet your buddy
5. Join the team's shared calendar
[Panel: "Your next induction session", read from the viewer's calendar]She shares it with Anyone at [organisation], Can view. It works for her. For Priya, the new starter, the panel shows a source-access error: Priya’s calendar connection isn’t set up, and the panel was reading the viewer’s calendar all along.
- The failure. The creator’s successful view proved nothing about Priya’s. The tempting fix was pasting the lead’s own induction events into the Artifact, which would have shown her calendar to everyone who opened it.
- The repair. The repair prompt removed the calendar panel and added “Your induction sessions are in the invitation from HR”. Priya reopened it: five items visible, ticking item 1 worked. That’s the example result at the top of this page.
- If the calendar really matters. Priya connects her own calendar under her organisation’s controls. She doesn’t inherit the lead’s.
Task kit for this job: Download (ZIP) · Reusable instructions
Go deeper
Optional training: Know what revoking access does
To restrict link access, open the Artifact, select Share and set Who has access to Only you (Pro, Max) or Only people invited (Team, Enterprise). On Pro and Max, existing email invitees keep their access after you choose Only you. Remove each invitee individually: open their access level and select Remove.
On Team and Enterprise, Only people invited keeps access for named invitees. If you change access to Only you, everyone invited from outside the organisation loses access and their invitations are removed. You can also remove a person individually through their access level. Deleting the Artifact removes access for everyone you invited. None of this recovers a copy someone already downloaded.
Legacy chat Artifacts work differently. On Free, Pro and Max, Unpublish revokes a published link, permanently deletes the Artifact’s stored data and prevents publishing that Artifact again. On Team and Enterprise, use Share › Unshare for a legacy chat Artifact.
Optional training: Know the rules for Claude Docs
Claude Docs have their own sharing limits. There’s no comment-only access level yet: viewers read, editors can also edit, comment and export. On Team and Enterprise plans, Docs can’t be shared outside the organisation at all, and Docs can’t be shared by email invitation on any plan. Check the Doc’s own Share dialog rather than assuming the Artifact options apply.
Optional training: Hand over the purpose as well as the link
Send a line or two with the link: what it’s for, which version you checked, what it doesn’t do, and what you’d like the recipient to do with it. When they need only the result and not the conversation behind it, see Share an AI result without sharing the whole conversation.