How to Share a Claude Design Link for Review or Handoff

To share a Claude Design link, open the design, choose Share, select who can open it and their access, then copy the link. Change sharing settings on Claude web or desktop, following Anthropic’s design guide↗ (opens in a new tab). Send a specific review request with it, so the recipient knows whether to inspect, comment, or revise.

A link gets someone to the design; a handoff explains what happens next. Tools like fenbs keep the approved direction, outstanding changes, and next step outside the design session, where another person or connected assistant can read them.

How do you create the share link?

1. Open the actual design you want reviewed. Check its title and contents before sending anything.
2. Choose Share and inspect the available audience settings. Select named recipients or a broader audience only as appropriate for this work.
3. Choose the access the recipient needs. Start with viewing for inspection; grant editing when changing the design is part of the request.
4. Copy the link from the sharing controls and send it with the design name, review scope, and next step.
5. Ask the recipient to confirm that the design opens in their account before relying on the link for a meeting or handoff.

Claude Design creates visual work as artifacts, the outputs that open beside a conversation. The broader Claude Design overview covers creating and refining that work; this guide focuses on sending its link with a useful handoff.

Which access should you choose?

Anthropic’s artifact sharing instructions↗ (opens in a new tab) distinguish Can view, Commenter, and Can edit, with available levels depending on the artifact. Shared artifacts require a Claude account, except for legacy published chat artifacts. Organization owners can restrict outside sharing, so check the options your account actually offers.

Treat those as different jobs. “Please review the layout” leaves room for confusion if the person assumes they should rewrite it. Say “Check the mobile layout and leave feedback; I will make the changes” when that is what you need.

Does workspace membership settle design access?

Check the design’s audience instead of assuming membership settles it. Someone can be the right colleague for a review while still opening the wrong account or following an old link. Send the design’s own share link, then confirm access with the intended person.

If the task is to give people access to the larger body of work, use the separate guide to sharing a Claude Design project with others. Keep this review request focused on the specific design, rather than inviting everyone into more material than they need.

For readers new to the app, what Claude AI is explains the surrounding tools. You do not need to explain the whole app in each handoff; identify the deliverable and tell the reviewer how to respond.

What should you send beside the link?

Include enough context to make the request answerable. Say a small studio is reviewing a new appointment page. The reviewer needs to know whether to judge its appearance, the booking sequence, or the wording. Asking for all three without saying so often produces feedback on whichever detail is easiest to notice.

• Name the design and the particular screen or state that needs review.
• State the question: for example, whether the booking confirmation makes the next step clear.
• Identify the reference being reviewed, such as a named revision and a dated export.
• Separate approved choices from unresolved questions, and name the person who will decide.
• Say where to leave feedback and who will turn accepted changes into revision tasks.

“Looks good” is difficult to build from. “The mobile booking sequence is approved; the confirmation wording still needs review” preserves both the agreement and the unfinished work. Keep that distinction in the project record when the design changes again.

fenbs keeps those decisions and remaining tasks with the AI handoff, so the next assistant can see what was approved before proposing another revision.

When should you send a file instead?

Use a file when the recipient needs a fixed reference for a meeting, an archive, or another workflow. Anthropic lists PDF, PPTX, standalone HTML, and ZIP among Claude Design’s export options↗ (opens in a new tab), plus a handoff to Claude Code. Choose the format for the recipient’s task, then open the exported result yourself before sending it.

A file and a live link need different labels. Mark an export as the reference reviewed on a particular date; say whether the link contains later changes. For implementation, the Claude Code overview explains the coding assistant, but the handoff still needs a person’s approved scope.

For older work at the standalone Claude Design address, consult Anthropic’s migration guidance↗ (opens in a new tab). It describes that version’s closure and warns that its public project links will stop working. Preserve the reference you need rather than treating an old URL as a permanent archive.

What if the recipient cannot open the link?

Ask what they see and which account they are using. Check the audience you selected, whether you sent the intended design, and whether the problem affects just that recipient. Avoid changing several settings at once: you want to know which condition prevented access.

If sharing is unavailable, check the current sharing documentation and ask the appropriate organization owner about restrictions. Do not broaden the audience merely to avoid an access problem. When a permitted export will satisfy the review, send that reference and keep the original audience intact.

How to do this with fenbs

1. Create a free account. fenbs is free for one person, no credit card; use a team kanban board when colleagues need shared access.
2. Add the project and a revision task. Include the design link, the reviewed reference, the requested change, and what still needs checking.
3. Record the person’s approved direction in Decisions and rules. Keep unanswered questions open, and add accepted revisions as tasks.
4. Connect a supported assistant through Integrations. Ask it to read the project context before working and save progress, including Where we left off, before stopping.

fenbs does not change Claude Design permissions or import its design comments. Keep visual editing in the design tool; if you only need to show one mockup, its share link or an export may be enough. Use fenbs when approvals and follow-up work need to survive a change of person or assistant.

Keep the next action small: one design, one review question, and one accurate handoff. See how fenbs works for the shared record, or explore the team AI brain guides when several people need the same project context.