How to Share a Claude Design Project With Others

To share a Claude Design project with others, open the design on Claude’s web or desktop app, choose Share, and set the access available for that artifact. If the recipient needs a deliverable rather than access to the working design, use Export and send the appropriate file. Anthropic’s Claude Design guide↗ (opens in a new tab) describes both routes.

Sharing the canvas is only part of the handoff. The next collaborator also needs to know which version is approved and what needs changing. fenbs keeps that feedback, the human decisions, and the resulting tasks available to teammates and connected assistants outside the design conversation.

What are the steps for sharing the working design?

1. Open the intended design on the web or desktop app. Confirm that it is the correct project and contains the version you want others to review.
2. Choose Share. Read the available audience and access choices for that artifact and your organization.
3. Invite the intended people where available, or select an appropriate link audience. Prefer named recipients for material that should reach only specific people.
4. Choose the access level that matches the request: viewing, commenting, or editing where offered.
5. Send the link with a short review request. Ask one recipient to confirm they can open the design using their own account before starting a larger review.

Anthropic’s artifact sharing instructions↗ (opens in a new tab) explain audience controls, access levels, and email invitations. The choices depend on the plan, artifact, and organization settings. Sharing settings cannot be changed in the iOS or Android app, so use the web or desktop app for this step.

If your project is in standalone Claude Design, expect a different interface from designs made inside Claude. Anthropic’s Design admin guide↗ (opens in a new tab) distinguishes those environments and their settings. Check which workspace you opened before following a screenshot or asking an administrator to change a setting.

Send a useful question along with the link. “Please review the contact form and tell us whether the required fields are correct” gives a reviewer a clear job. “Thoughts?” often mixes copy edits, brand concerns, and approval into one conversation, leaving the designer unsure which comments are instructions.

Who should be allowed to view, comment, or edit?

Give access according to the work being requested. A stakeholder approving the layout may only need to view it. A reviewer needs a way to leave feedback, while a collaborator making changes needs editing access. Check the specific options in Share; do not assume that every artifact offers identical permissions.

Agree who edits at a time during a shared review. The Design guide warns that simultaneous editing by multiple people remains basic and may be unreliable. Collect feedback first, then give one person responsibility for applying the agreed changes.

For organization accounts, external sharing also depends on what an owner has enabled. If an outside collaborator cannot be invited or the link setting is unavailable, ask the owner to review the intended sharing arrangement. Passing around your login is not a substitute for granting the right access.

Treat audience and authority as separate choices. A person allowed to edit the canvas is not automatically the person authorized to approve the final design. Write that approval responsibility down. The team brain guides explain how to give people and their assistants a common record of those responsibilities.

When should you send an export instead?

Anthropic lists PDF, PPTX, ZIP, standalone HTML, Google Slides, and Claude Code handoff among the export options in its Design guide. The available route should serve the recipient’s job. A PDF is useful for a stable review but will not communicate every interaction that matters in a working prototype.

Open the actual export before sending it. Check labels, images, links, and the behavior the reviewer is supposed to assess. A successful download is not evidence that the handoff works. Name the file clearly and include the review date so feedback on an older copy does not silently become a request against the current design.

An export is a separate copy, so removing access to the original should not be treated as retrieving files someone already received. Keep that practical distinction in mind when deciding whether to distribute a file or keep a review inside the shared workspace.

How do you hand over the design system?

A design project is one output; a design system is the reusable set of colors, typography, components, and layout patterns behind many outputs. Sharing an example does not prove that the recipient has everything needed to reproduce it. The broader Claude Design overview explains what the tool makes.

Follow Anthropic’s design-system setup guidance↗ (opens in a new tab) for the environment you use. It describes building a system from source materials, using code components through Claude Code, and managing organization design systems. Organization settings can limit who publishes a system or makes it the default.

For a handoff, identify the source of the system and the person who maintains it. Include the correct logo files, approved type choices, component references, and any exceptions the recipient needs. Confirm that you have permission to share the assets themselves, especially licensed fonts or client material.

Test the handoff with one small output. Ask the collaborator to create a simple page using the intended system, then compare the result with the approved example. Record any mismatch as a concrete correction rather than describing the whole result as “off brand.” A reusable rule in the fenbs work record can explain the required behavior to the next connected assistant.

What should travel with the link or files?

Send a short handoff note that answers four questions: what is this, which version should we use, what has a person approved, and what is still open? Include a clear request and a named reviewer. Keep the source design distinct from exported copies so everyone knows where future changes belong.

• Purpose: the audience and the job this design needs to perform.
• Status: approved direction, work in progress, or an option for discussion.
• Review request: specific questions and the person who will resolve feedback.
• Remaining checks: responsive behavior, text, accessibility, links, or implementation details that have not been verified.

Do not treat a shared design as a complete record of the conversation behind it. Preserve the relevant reasoning in the handoff note, rather than assuming recipients can reconstruct the history. For ongoing delivery, Claude for project management covers the surrounding work, while Claude project memory covers context inside projects.

How to do this with fenbs

1. Create a free account. You can start alone for free, with no credit card; use a team kanban board for shared work with colleagues.
2. Add a project for the design and tasks for the changes or checks still required. Put the source design reference in the project context.
3. Record the human approval in Decisions and rules, naming the person who chose the direction. Keep unanswered design questions open.
4. Connect a supported assistant through Integrations and ask it to read the project context before proposing or implementing changes.
5. Save progress with the current version, completed checks, and next review step so the next session begins from the same state.

fenbs does not edit the Claude Design canvas or change its sharing permissions. If you only need a one-time visual review, the design’s own sharing controls or an export may be enough. Add a shared work record when approvals, follow-up tasks, and different AI apps make the handoff harder to track.