Docs/Client Feedback

Client Feedback

Share a time-limited link. Clients browse your dev theme and drop visual pin comments directly on the page — no login, no app, no friction.

How it works

  1. Open the Feedback tab inside a theme
  2. Click New Feedback Session, set an expiry (1 hour to 30 days), and copy the link
  3. Send the link to your client
  4. They open it — a lightweight toolbar appears over the preview site
  5. They click anywhere to drop a pin and type a comment
  6. You see all comments in real time in the Feedback tab

Feedback Sessions

A feedback session is a timed, secure link scoped to one theme.

PropertyDetails
Expiry1 hour to 30 days — set when creating the session
AuthNo login — anyone with the link can comment
SecurityCryptographically random token, not guessable
RevokeClose the session early from the Feedback tab
ExtendRe-open an expired session with a new deadline
Separate sessions per round Create a new session for each review phase — "Round 1 – Layout" vs "Round 2 – Final Polish". Comments stay organised by round and you get a clear history.

Feedback Overlay

When a client opens the feedback link, a lightweight toolbar appears at the top of the preview:

  • Pin mode — click anywhere on the page to place a comment pin
  • Free navigation — browse any page on the theme naturally; drop comments anywhere
  • Device-aware — each comment is tagged with the viewport it was made at
  • Name entry — optional name and email so you know who commented
  • Approval buttons — clients can approve individual pages directly from the overlay

Comments & Pins

Each comment captures full context:

  • Precise position — pinned to the exact element on the page
  • Page context — which URL, which viewport size, which browser
  • Threaded replies — you and the client can discuss back and forth on each pin
  • Resolve / reopen — mark as fixed, reopen if the fix doesn't land correctly
  • Sequential numbering — pin #1, #2, #3 for easy reference during calls
Approvals blocked by open comments A page cannot be approved if it has unresolved comments at that viewport. Resolve comments first, then approve.

Page Approvals

Feedback sessions include the same multi-role approval matrix as QA. Each page is approved per viewport per role:

  • Client — approves via the feedback overlay on the preview link
  • Designer — approves visual fidelity from the Feedback tab
  • QA — approves cross-browser correctness
  • PM — final sign-off on scope and requirements

The Feedback tab shows a progress view — how many pages are fully approved across all required roles and viewports.

Reject with reason Shift-click any approval slot to reject instead. A reason field appears so the specific issue is documented before re-review.

Exporting Feedback

Export all feedback from a session as structured JSON from the Feedback tab. The export includes:

  • All comments with page, position, and viewport context
  • Resolution status and timestamps
  • Approval decisions — who approved, which role, when
  • Client identity (if they provided a name)

Import into Linear, Jira, Notion, or any project management tool — or archive for the project record.