Should I send the entire conversation to a client?

Only when the conversation is useful and appropriate for that client. A reviewed excerpt or finished file is often clearer, especially when the discussion includes discarded ideas, internal notes, or information unrelated to the review.

Is sending a link enough to assign the next task?

Include an explicit request, the relevant version, and any approval or check still needed. A recipient should be able to tell whether you want feedback, a revision, or continued implementation without reconstructing the discussion.

What should I do before replacing a shared draft?

Decide which version is current and tell reviewers what changed. Preserve the approval context and update the next task so someone returning later does not act on an outdated copy.

Will fenbs copy the conversation for my teammates?

No. fenbs does not import Claude chat history. You save the reviewed work record, including tasks, decisions, and progress, and provide references that the intended recipients can access separately.

How to Share in Claude: Chats, Files, and Project Access

Choose between a conversation snapshot, an output file, an artifact, and project access. Here is how to send the right thing and keep the follow-up work clear.

July 24, 2026Updated October 21, 20266 min read

To share in Claude, choose the thing the recipient needs: a conversation link, a reviewed transcript or file, an artifact, or access to a shared project. Use that item’s sharing controls, then check the audience and what the recipient can open before sending it. A link to an answer and permission to work on a project solve different problems.

Tools like fenbs keep the team’s decisions and next steps beyond the link, so the person receiving an output also knows what to do with it. Start by deciding whether you want someone to read, review, edit, or continue the work.

What are you trying to give the other person?

Choose the smallest useful package. Send an approved paragraph when that answers the request; include the conversation only when the reasoning matters.
Review the material for private details, unapproved claims, and earlier suggestions that could be mistaken for the final answer.
Choose the audience and access in the relevant Share menu, or send a reviewed file through your usual document-sharing process.
Ask the recipient to confirm that they can open the material and understand the requested next action.

Choose by what the recipient needs to do
Your goal	What to send	What to explain
Show how you reached an answer	A conversation snapshot or selected transcript	Which conclusion you want reviewed
Deliver something finished	A reviewed output or exported file	The version and intended use
Review an interactive result	An artifact with suitable access	Whether feedback or editing is expected
Work from common background	Project access, where available	Which source material is current

If the product names are unfamiliar, the Claude overview explains the starting point. For ongoing team work, how fenbs works shows how a shared project record complements the material you send.

What does a conversation link actually show?

Claude’s chat-sharing guide (opens in a new tab) describes a snapshot made from the chat’s Share menu. It includes messages up to sharing, including artifacts, while later messages stay private unless you update the shared version. Team and Enterprise chat sharing stays within the organization.

Uploaded attachments and raw data from connected-tool calls are excluded from that chat snapshot. The visible conversation can still contain quotations, summaries, or details drawn from those sources. Review the actual messages rather than assuming that an excluded file makes its contents absent.

For example, a draft may quote a customer’s address even though the uploaded document itself is unavailable. Remove the detail from the material you intend to send, or prepare a separate reviewed summary. The focused guide to sharing a Claude chat covers that particular route.

How do you send only the useful output?

When someone needs the answer rather than the discussion, copy the relevant text into a document you can review. Label it as a draft or approved version, preserve any necessary source references, and remove discarded options. A short introduction should say what the recipient is being asked to check.

For an artifact, open its own Share menu and check the audience and access options. Claude’s artifact-sharing documentation (opens in a new tab) distinguishes viewing, commenting, and editing, with availability depending on the artifact and account. Change those settings on the web or desktop app. Current shared artifacts require a Claude account, with an exception for legacy artifacts published from chat.

Treat legacy chat artifacts separately: Anthropic warns that sharing one can also expose the attachments and files in its originating chat. Do not apply the chat-snapshot attachment rule to an artifact link. Inspect the relevant sharing screen before sending either kind.

If you need a transcript archive, Claude offers account data export (opens in a new tab) through Settings, then Privacy, on web or desktop, subject to organizational controls. Review the resulting material and share only the intended excerpt. Sending an entire account archive is usually more information than a teammate needs.

When should you give project access?

Choose project access when colleagues need a common set of reference material and instructions for ongoing work. Claude’s project-sharing guide (opens in a new tab) describes this for organization accounts, subject to administrator settings. Open the project’s Share menu, add the intended members, and choose Can view or Can edit.

Can view includes using the project in chats; Can edit allows changes to its instructions, knowledge, and member settings. Project access does not automatically expose everyone’s private conversations. Also, a project labeled public means visible within the organization in this context, rather than published to the open web.

Write a short orientation for a new member: the goal, the approved reference, and the question still open. For visual work, the Claude Design guide explains the separate design workflow. Giving access is only the first step; the recipient still needs to know which part of the work is ready to use.

What should you check when a link does not work?

Start with the object and account involved. Ask whether the link points to a conversation, an artifact, or a project, then compare the signed-in recipient with the audience you selected. A copied address alone does not establish that the intended person has access.

Confirm that the recipient is using the intended account and, for organization work, the intended organization.
Reopen the original item’s sharing settings. Check whether access was removed or whether an administrator controls the missing option.
Check the version. The sender and recipient may be looking at different snapshots, exports, or copies.
Test the actual task: opening the item, leaving feedback, or editing. Success at opening a page does not prove that the requested action is available.

Avoid broadening access just to make an error disappear. If the recipient only needs a paragraph, a reviewed excerpt may be the appropriate handoff. If they need ongoing access, ask the owner to review that specific access request.

How do you keep the follow-up work clear?

A useful handoff says what the material is, what a person approved, what remains uncertain, and what happens next. Say a studio shares a draft landing page: “Please review” leaves room for several interpretations. “Check the mobile form; the headline is approved; submission delivery is untested” gives the recipient a concrete job.

Keep that instruction with the project’s work record and reference the shared output. When implementation is next, the Claude Code guide explains that coding tool. Whoever continues should be able to distinguish an approved requirement from a suggestion in the original discussion.

fenbs supports that AI handoff through tasks, Decisions and rules, and Where we left off, so the next connected assistant has a clear starting point.

How fenbs helps

Give the shared link a clear next step

Create a project in fenbs, reference the reviewed Claude output, and add the remaining revision tasks. Record what a person approved in Decisions and rules, then save Where we left off before stopping. Your teammate’s connected assistant can read the work record before continuing.

Create a free account

Free for one person · No credit card · Works with Claude, ChatGPT, Cursor and more

How to do this with fenbs

Create a free account. fenbs is free for one person, with no credit card; use a team kanban board when colleagues need access.
Add the project and a task describing the next action. Reference the Claude link or the approved file’s location in the task, with enough detail to identify the version.
Record the person’s approval in Decisions and rules. Keep open questions separate, so an assistant does not treat a draft suggestion as an agreement.
Connect a supported AI app through Integrations. MCP is a standard way for an AI app to use an outside tool; fenbs connections use browser sign-in.
Ask the assistant to read the project context before working and save progress when it stops. Include completed work, checks still needed, and the next step.

fenbs does not import your Claude chat history or grant anyone access to a Claude link. If you only need to send a finished document once, your usual document-sharing process may be enough. For continuing work, the shared team brain guides explore how to keep the same project understanding across people and assistants.