Turn one review comment into the next candidate
Invite focused feedback on an exact saved revision, then continue privately from the comment while keeping the reviewed source available.
Start creating in Chat ↗Follow a comment back to its source
Illustrative food-night review: the comment belongs to the announcement revision the guest saw.
Ask for focused feedback
Choose the announcement revision and preview its bounded guest view. A reviewer asks to shorten the opening while keeping the event date. Their comment stays attached to that saved version.
Try the suggested change privately
An authorized editor opens the comment, starts a branch from the reviewed source and prepares a shorter draft. Compare the new candidate with the original before choosing it.
Feedback stays with its source
A comment does not approve or overwrite a newer draft. Read focused review for the access boundary and the continuation guide.
See an example workflow
An illustrative example. Review current inputs, settings and the quote in your workspace.
- StartChoose the exact announcement revision for a guest comment.
- Request or actionRead the comment and branch privately from that revision.
- ReviewConfirm the requested change and check preserved facts.
- Saved resultA revised draft beside the reviewed original.
- ContinueCompare and choose; the guest comment remains on its source.
Example AskGL request
Shorten this announcement opening as requested in the review. Preserve the approved event date and venue.
Replace sample facts with approved details. Source selection and later review, comparison or packaging happen in the workspace, outside the prompt text.
Continue this work
Good to know.
Creation notes
Prepare your starting point
Explain what the reviewer should judge, such as clarity or product framing. Select the exact revision and use the bounded guest-review controls. Decide whether a suggestion fits the brief; a review link does not grant unrelated workspace access or automatically change the source.
Understand bounded reviewReview what you keep
Describe the intended revision and the details that must remain intact. Review the next request and compare the whole saved output with both the original and the comment. Keep the source evidence when accepting or rejecting the new direction, instead of silently replacing the reviewed version.
Branch from review feedbackCommon questions
Does saving the result publish it?
Saving keeps the output in the workspace. Download, content-set delivery and activation of an eligible public release are separate supported actions.
Are the public story assets generated results?
The public boards are labeled layout placeholders. They explain the story and review decisions, not live-provider quality. Inspect the actual saved result in your workspace.