Skip to main content
An answer is rarely useful only to the person who asked for it. Upsolve gives end users two ways to hand an analysis to someone else, both producing a plain URL that opens in a browser with no Upsolve account required.

​
Share one answer

Next to the thumbs up / thumbs down on any answer, a share icon opens the share dialog for that exchange. The user picks which parts of the answer travel with the link: Only the parts the answer actually produced are offered — an answer with no chart won’t offer Chart. This is what makes the feature safe to expose to end users: someone sending a summary to a non-technical stakeholder can leave Details off, and the recipient never sees SQL or column names.
The share modal for a single answer, with checkboxes for the question, analysis, chart and details, and a row of link-expiry options
Every share link carries an expiry, chosen when the link is created:
  • 24h (the default)
  • 7 days
  • 30 days
  • Never
The dialog offers Copy link and Copy and open, which copies the URL and opens the shared page in a new tab so the sender can check what the recipient will see.

​
What the recipient sees

The link opens a clean, standalone report page at /share/analysis/{id} — the question, the narrative, the chart, and the details, in that order, with none of the chat interface around it. The page has a Print action, so the recipient can save it as a PDF or drop it into a deck.
A shared analysis page showing the question, the written insights and the chart as a standalone report, with a Print action in the header

​
Share the whole conversation

Some analyses only make sense as a sequence — the user narrowed down through four questions, and the fourth answer is meaningless without the first three. For those, the Share chat button in the top-right of the chat pane shares the entire conversation. It takes the same expiry options and produces a link to /share/chat-history/{id}, which renders the full thread — every question and every answer, with the charts — as a read-only page.
The Share chat button above a conversation, with its modal open showing the link-expiry options
Both share types are point-in-time snapshots of the conversation as it stood when the link was created. They do not re-run the SQL when opened, so the recipient sees the numbers the sender saw. If you need a shared view that refreshes against live data, use a Canvas in live mode instead.

​
Shared chats your users can continue

A conversation shared through an agent’s shared-chat page (/share/chat/{agentId}) is more than a transcript: the recipient can pick the conversation up.
  • If they were the original participant, they get Continue conversation — the thread resumes with all its context.
  • If they weren’t, they get Fork conversation — a copy of the thread is created under their own identity, and they carry on from there without altering the original.
The same continue/fork behaviour appears wherever a saved analysis links back to its source conversation. See Favorites for the details.

​
What the builder sees

A shared analysis is still a conversation, so it appears in Chat History like any other, and its Shareable Report step shows up in the observability trace. Sharing itself isn’t a separate surface you have to monitor.

​
Next steps

Favorites

Save an answer for later instead of sending it now.

Canvas

Assemble saved answers into a board and share that instead.