feat(conversations): allow one-way private to public publish - #1545
Draft
sentry-junior[bot] wants to merge 5 commits into
Draft
feat(conversations): allow one-way private to public publish#1545sentry-junior[bot] wants to merge 5 commits into
sentry-junior[bot] wants to merge 5 commits into
Conversation
Add a participant-only SQL mutation that flips the root destination visibility to public, and expose it in the conversation UI with an irreversible confirmation. Co-Authored-By: David Cramer <david@sentry.io>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Dashboard visual evidenceMode: path-selected Triggered by:
Conversations · desktop
Conversations · mobile
Conversation detail · desktop
Conversation detail · mobile
Component gallery · desktop
Full-page screenshots from the mock dashboard. Not a pixel-diff gate. |
![sentry-warden[bot]](https://avatars.githubusercontent.com/in/2755838?s=60&v=4){kind=small}
Refuse one-way destination publish when other roots share the same destination so a single thread cannot expose unrelated private conversations.
dcramer
reviewed
Aug 14, 2026
| onClick: () => { | ||
| if ( | ||
| !window.confirm( | ||
| "Make this conversation public? Anyone with the link can read it. You cannot undo this.", |
Member
There was a problem hiding this comment.
thats not quite true, they still need logged in, no?
Contributor
Author
There was a problem hiding this comment.
yep — still needs a workspace login. updated the confirm copy to match the privacy chip: "Anyone in this workspace can read it."
Public conversations remain workspace-authenticated. Match the privacy chip wording so the confirm does not imply anonymous link access.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Participants can make a private conversation public from the conversation UI.
This is a one-way SQL flip on the root destination visibility. There is no public-to-private path.
Why
Private dashboard conversations needed a simple escape hatch so someone who can already see the transcript can share it.
What changed
POST /api/conversations/:id/publishrequires an authenticated participantjunior_destinations.visibilitytopublicfor the conversation rootNotes
Visibility still lives on the destination row. Shared destinations publish together. No migration.
Requested by David Cramer.
--
View Junior Session [Sentry]