Comments and change requests

Keep review discussion with the images it concerns.

Discuss a result#

Open the discussion panel on a run or story. Explain what changed, whether it was expected, and which state or variant needs attention. Use links to the run when bringing teammates into the review.

Company viewers can read results. Reviewers, members, admins, and owners can comment; only members, admins, and owners can accept or reject visual changes.

Request changes#

Use a change request when the author needs to take action. A discussion note and a visual approval are different actions. Inspect the run summary for outstanding requests even after screenshots have been accepted.

When the fix arrives, inspect the new result and clear the request through the review controls. A successful upload does not resolve a requested change by itself.

Assign the right reviewer#

Use the run's reviewer controls where available to make ownership clear. Invite a designer as a reviewer if they should discuss changes without approving the visual baseline, or as a member if they should accept and reject screenshots.

Keep sensitive data out#

Comments are visible to the company members who can access the project. Do not paste tokens or customer records. Use synthetic fixtures when a screenshot needs to illustrate a problem.