Skip to content

BlogHow-to

How to collect client feedback without a login

Clients leave more feedback when they don't need an account first. What a review without a login needs, how to set one up, and what to check before you send the link.

DinoFounder of layernote · Nov 20, 2026 · 3 min read

Most clients won't make an account to leave a few comments on your work. When the review tool asks for one, the feedback often comes back by email or in a call, and someone has to work out which part of the page it is about. This post is about the other way: one link that the client opens in a browser and comments on right away.

Why a login gets in the way

A client reviews your work a few times per project. For them an account is one more password for a tool they open twice. Some will make one. Others send the link on to a colleague, or write their notes in an email.

Every step before the first comment costs you some reviewers. The account is usually the biggest step, and it is the one you can leave out.

What you still want without a login

Leaving out the account is only half of it. Check that you still get these:

  • A name on every comment. With several people on the client side, you need to know who asked for what.
  • Comments on the work itself. Pinned on the element, the PDF page or the moment in the video, so nobody has to describe where they mean.
  • Control over the link. Who can comment, who can only look, and a way to close the round.
  • No seat per reviewer. If every client contact costs a seat, people end up sharing one login, and the names are gone again.

How it works in layernote

I make layernote, so consider the source. This is how a review without a login goes there.

  1. Make a project for the work: a live website by its URL, or uploaded images, PDFs and videos.
  2. Click Share in the project header.
  3. Under Reviewers can, choose Comment.
  4. Copy the link and send it. Or type the client's email addresses in the same dialog, and layernote sends them the link with your note.
The Share dialog: the link, email invites, and who can comment or only look.

The client opens the link in their browser and sees the site or the files, with the comments that are already there. When they place their first comment, layernote asks for a name and an email address. That is all: no password to pick and nothing to sign up for. Their comments carry the name they typed and are marked as coming from a guest.

A client pins a comment on the spot they mean.

Reviewers who come in through a link take no seat, on every plan. Five people on the client side cost nothing extra.

All of these are in the same Share dialog.

  • View only. For people who should see the state of things without adding to it.
  • A password. For work that isn't public yet. Changing the password locks out everyone who had the old one.
  • A feedback deadline. People you invited by email get reminders before it.
  • Pause commenting. When the round is done. The link still opens, but no new comments come in until you switch it back on.

There are trade-offs. It is better to know them before the review starts.

  • Anyone with the link can open it. A forwarded link works for the next person too. Set a password when that matters.
  • The name is what the reviewer types. There is no account behind it. layernote does refuse an email address that already belongs to an account, and asks that person to log in instead.
  • Reviewers give feedback, your team acts on it. Guests can comment and reply. Assigning, resolving and setting a status stay with the people in your workspace.

After the feedback is in

Every comment lands in the project as an open item. You fix each one yourself, or hand it to Claude or your coding agent over MCP.

The client sharing docs cover every setting of the link, and the website feedback tool page shows what a review looks like for the client. For how to ask for feedback you can build from, see how to get design feedback from clients you can actually use.

Read nextLet clients pin feedback from one link, no account needed
Written by DinoFounder of layernote · @dino_murs on X

More from the blog