client-review
How clients review your work
The two ways a client reviews your work without an account — a share link for deliverables and a proposal link for accepting or declining a proposal.
Updated 23 June 2026
Clients review your work through two kinds of link, both opened in any browser with no login and no account. You send the link; the client opens it; they see only the work you chose to share.
The two links do different jobs:
- Share link — the client reviews a deliverable. They view it, leave comments, mark up the image, and (if you allow it) approve it or request revisions. See Reviewing a deliverable on a share link.
- Proposal link — the client reviews a proposal you sent and either accepts or declines it. See Accepting or declining a proposal.
Both open on portal.imeshh.com. Neither asks the client to sign up. Each link shows only what you chose to share — the client never reaches your dashboard, your other projects, or another client's work.
Which link to send
Match the link to the decision you need from the client:
| You want the client to… | Send a… |
|---|---|
| Look at a render and give feedback | Share link |
| Approve a deliverable or ask for changes | Share link with Can approve permission |
| Decide whether to go ahead with a quoted job | Proposal link |
A share link is about the work in progress. A proposal link is about the deal. A client often gets both over the life of a project — a proposal first to agree the job, then share links as deliverables come through.
What a link can never reach
Both links are scoped tightly on purpose. Whichever link a client holds, they cannot:
- See any other project, deliverable, or proposal you have not shared with them
- See your dashboard, pricing, plans, or settings
- See another client's links or content
- See your internal notes — notes you add for your own team stay hidden from every client view
If a client needs to see a second deliverable, send a second share link. If they need a revised proposal, send a new proposal link.
Treat the link like a password
Each link holds a long, random token that cannot be guessed. Anyone the client forwards it to gets the same access, so handle it the way you'd handle a password.
What's next
- Reviewing a deliverable on a share link — view, comment, mark up, approve, and request revisions
- Accepting or declining a proposal — packages, add-ons, the total, and the Accept or Decline decision