You sent a client a review link. Before they look at anything, the first question lands in your inbox: do I need an account to leave feedback? The short answer is no. Here is what actually happens on a shared Cobalt Capture link, broken down the way people ask about it.
Do I need to sign in to read a review someone shared with me?
No. Anyone with the link can open it and read every item: the screenshots, the pins and arrows baked into them, and the comments underneath. There is no password, no account prompt, and no app to install. The link opens in whatever browser they already have, on a laptop or a phone.
If your reader just wants to scan the findings without the editing interface, send them the clean read page at /s/<slug>. It strips the review down to what they need to see. The main /r/<slug> link works the same way for reading, and it is what you share when you want comments back.
Can an anonymous person comment on an item without an account?
Yes. Anyone holding the link can leave a comment on any individual item in the review. They do not create an account, they do not get a password, and they do not have to learn a tool first. They open the link, find the screenshot in question, and type under it. That is the whole point of sending a client a link instead of inviting them to a client feedback workflow that makes them register before they can say anything.
Comments attach to the specific item, so when your client writes "this button is the wrong green," that note sits on the screenshot of that exact button, not in a separate email thread you have to reconcile later. If you want the full picture of what a client sees the moment they open the link, there is a walkthrough of the client view.
Who can mark a comment resolved?
Only the signed-in owner of the review can resolve comments. An anonymous commenter can leave feedback, but they cannot close it out. This split is deliberate. The person who owns the work decides when a piece of feedback is handled, so resolving stays in one pair of hands and nobody wonders whether a comment was closed by accident.
When you resolve a comment, it is marked done on your end while the thread stays readable for the people who were in it. Cobalt is not a bug tracker with assignees and workflow states, so there is no ticket to move across a board. There is just a comment and a resolved mark. If you want the mechanics of keeping feedback tidy this way, see how to resolve review comments without a bug tracker.
Who sees whose comments?
Everyone with the link sees the comments on the review. There are no private side channels and no per-person visibility. If you send one link to a client and a developer, both of them read the same thread. That is often what you want: the client flags something, the developer replies under the same item, and the conversation stays in one place.
If you would rather keep two audiences apart, make two reviews or send two different links. Cobalt does not run multi-reviewer sessions where people edit together live, so the model stays simple: one link, one shared set of items, comments visible to anyone who holds it.
Does the link keep working, and for how long?
This is where honesty matters, because "free to try" is not the whole story. Cobalt is free to start with no password and no credit card, and the shared link keeps working for the people you sent it to, comments included. Nothing gets deleted.
The limit is on the owner, not the reader. Seven days after you create a review, it goes read-only for you: editing, exports, and agent access stop. Your client can still open the link, read it, and comment on items the entire time. If you need to keep editing past that window or reopen a review you let lapse, Pro is $5 a month or $50 a year, and you can cancel any time. The exact terms are on the pricing page.
Can my client comment from a phone?
Yes. The link opens in a phone browser with no app to install, and your client can read every item and comment on any of them from there. Reading and commenting work the same across devices. The one thing phone browsers cannot do is capture a screen, but a reader who is only leaving feedback does not need to capture anything. For the sending side of that, here is how to send a review link that opens on a phone.
What is the fastest way to collect this feedback?
Capture the screens your client needs to react to, pin the exact spots, publish, and send the link. Your client opens it, comments on the items that matter to them, and you resolve each one as you handle it. No tool to onboard, no login to chase. If you want to start now, open a new review and share the link the moment it is ready.