Statuses and approval
How feedback moves from open to resolved, who can close it, and who gets emailed.
Screenshots before and after the fix
The client's screenshot shows the problem. Once it's fixed, add one of how it looks now, so they can compare before they approve. On the feedback page, the Screenshots tab has Before and After the fix: choose, drop or paste a picture (you can add your own from before the fix too). Mark done takes one as well. On the site, a pin's ⋯ menu has Add a screenshot of the fix, which captures the page as it is with the element outlined. Coding agents upload theirs with upload_screenshot. The client sees them in the conversation, on the site and in the dashboard, and the “please check” email mentions them.
Adding feedback in the dashboard
Not everything is said on the site. On a project's board, press New feedback (or Add feedback under New) to add an item by hand, like an issue in Jira: what should change, the page, a screenshot (paste it with Ctrl+V, drop it, or choose a picture), a voice note recorded right there, and files. The team also sets the priority and who does it. Clients can add feedback the same way from their board.
These items aren't pinned to an element. They show in the list on the site, and the team can pin one later from its ⋯ menu (Re-pin to another element). Everything else works the same: statuses, replies, emails, Jira and AI agents.
Statuses
| Status | Means |
|---|---|
| Open | Reported, nobody has started. |
| In progress | Someone is working on it. |
| Needs info | The team asked the client something. The client's answer moves it back to In progress. |
| Ready for review | The team says it's fixed; waiting for the client to check. |
| Resolved | Done. The pin is hidden on the site. |
Client approval (on by default)
With The client approves fixes switched on in project settings, feedback from a client is closed by that client: the team moves it to Ready for review, and the client clicks Looks good. Members can't close it themselves. Owners and admins can, and the history notes that it was closed without the client's approval.
Switch the setting off to let anyone on the team close feedback directly.
Emails
- New feedback: everyone in the workspace (can be turned off per project).
- Ready for review: the person who reported it, with a link to the pin on the address where the fix is.
- Needs info: the client, with the question and a link to answer.
- Client approves, says it's still broken, or replies: the assignee, or the whole team if nobody is assigned.
- Team replies to a client's feedback: the client.
- Assigned to you: you.
Nobody is emailed about their own action. Clients only get email if they left an address.
Conversation and history
Every feedback item has a thread. Clients reply from the pin; the team replies from the pin or the dashboard. Status changes, assignments and re-pins are recorded alongside.