That is a claim about documentation, which is the only kind of claim worth making here. Anthropic's page on publishing and sharing artifacts is the page that enumerates the settings, and the word “password” does not appear on it. The documentation does not describe a setting for choosing when an individual link expires. Read on 4 November 2026.
What Claude does offer
| Control | What it does |
|---|---|
| Audience, Pro, Max and Ultra | “Only you” or “Anyone with the link”. Two settings, no middle ground. |
| Audience, Team and Enterprise | “Only people invited”, “Anyone at” your organisation, or “Anyone with the link”. The last one needs an owner to turn on External sharing or allow that artifact individually. |
| Access level | Can view, Commenter or Can edit. Some kinds of artifact offer only view or edit. |
| Invite by e-mail address | In beta on Pro, Max, Ultra, Team and Enterprise. The closest thing to a per-person gate: an invitation works only for the person invited, who must sign in with that address. Up to 50 people per artifact. |
| Allowed domains, on an embed | Lists the websites that may embed a published artifact. It governs embedding, not who can open the artifact’s own link. |
| Version pinning | A link can show the latest version or one specific version. If you share the latest, viewers see your changes as you make them. |
The invitation route is documented separately. Worth knowing: a pending invitation expires after 30 days, an accepted one never does, and if the artifact is also shared with “anyone with the link” then the people you invited get the same access as everyone else regardless of the level you gave them.
Why that is a gap
“Anyone with the link” is a reasonable default for a prototype. It is the wrong setting for a pricing page, a term sheet or a client report, because the link outlives the conversation: it gets forwarded, pasted into a thread, and opened by people you never picked. The other option is to require every reader to hold a Claude account, which your client probably does not. Between “anyone” and “only Claude users” there is nothing.
The HTMLRadar route
Download the artifact as a single, self-contained HTML file.
Upload it to HTMLRadar, or ask Claude to publish it for you through the connector.
Create the share link and set what it should ask for before it opens. Send that link instead of the artifact.
| Per-link setting | What the reader meets |
|---|---|
| Password | A password box before the document opens. At least eight characters, and we store only a hash of it. |
| E-mail gate | The reader gives an address before the document opens, and that address is attached to everything they read. |
| Allow-list | Named addresses, or whole e-mail domains; add the one-time code so each reader proves the address is theirs. |
| Expiry date | After the date you set, the link stops serving the document. Nothing to remember to switch off. |
| Revoke | Closes one link immediately, without touching the others. |
Where this does not help
A password on an HTMLRadar link protects the copy HTMLRadar serves. It does nothing to the artifact still sitting in Claude, so if you already published that one, unpublish it or you have two doors and only one lock. And if the artifact needs Claude to run (it asks Claude questions, reads a connected tool, or keeps stored data), exporting the HTML gives you the page without the behaviour. Those belong in Claude, with Claude’s own sharing settings.