Why feedback scatters
The usual loop sends a PDF by email and gets feedback back as voice notes, screenshots and “the chair in the third photo”. By the third round nobody is sure which version “the second option” was. The fix is not more discipline; it is putting the feedback on the work itself.
The loop on one canvas
- Share the file with one link
Open Share and copy the link. The client opens it in the browser, like a Figma file, and sees the canvas as it is right now; no account needed to view.
- The client comments on the image
Comments are pins: they land on the exact spot they are about, the armchair or the pendant, not “somewhere in picture two”. Signing in to comment is free.
- Iterate where they watch
Change the render in a sentence, right next to the comment that asked for it. The new version lands beside the old one, so “before and after” is something you both point at.
Bringing the right person in
Mention someone with @name inside a comment and they get notified. In a project with a client, a partner and a contractor, that keeps each thread pointed at the person who can answer it, still on the same canvas.
Keep every option on the canvas instead of deleting the rejected ones. When the client asks “what was the second option again?”, the answer is a glance, not an email search.
Who can do what
Workspaces have roles (owner, editor, viewer, guest), and inside a single project a person can be a viewer, commenter or editor regardless of their workspace role. The usual client setup: the client views and comments, your team edits. Roles are covered in Workspaces, people and roles.
Where to go from here
Sharing mechanics, link permissions and comment details live in Sharing and commenting. For the full picture of client collaboration in Hiera, see the client collaboration page, or open the app and share your first file; the workspace is free.
