The problem: the screens nobody outside can see
A marketing site can be reviewed by anyone with the address. The signed-in side of a product cannot: the dashboard, the settings pages, the admin panel, the internal tool. Feedback tools that fetch your page from their own servers and show it inside their own frame see a sign-in screen and nothing else. So feedback on the part of the product people use all day falls back to screenshots in a chat thread, each one missing the address, the element and the size of the window.
Why ClickNote works behind a sign-in
ClickNote does not fetch your pages. Its snippet is one script tag on the page itself, so it runs in the reviewer’s own browser, in the session they are already signed in to. ClickNote never holds a password for your app, never signs in to it and does not load it through a proxy.
<script src="https://feedback.youragency.com/l.js" data-project="PROJECT_ID" async></script>The script is under 1 KB and stays idle until someone opens the project’s review link: for everyone else it makes no request and changes nothing on the page. When a reviewer has opened the link once, their browser remembers it for that site, and the review tools load on every page that carries the snippet.
How to set it up on a web app
- Make a project with your app’s address as its site address. If staging and production are on different addresses, list the others under the project’s other addresses: notes are accepted from the addresses you list and from nowhere else.
- Add the snippet to the HTML document every screen shares. In a single-page app that is the one document every route is drawn into. Include the sign-in page if you can.
- If your app sends a Content-Security-Policy, allow your ClickNote address in
script-srcandconnect-src. The install guide has the header. - Sign in to your app, then open the review link in the same browser. The link leads to the project’s site address and switches the review tools on there. Confirm your email address with a one-time code: that is ClickNote’s own check of who is leaving notes, and it is separate from your app’s sign-in.
- Click any element and write the note. Use Browse mode to move through the app as usual, then Comment mode to pin the next note.
The dashboard’s Check the site button cannot confirm a snippet behind a login, because it sees only what your app serves to a visitor who has entered no password. Opening the review link on the app does the same job: the first time the review tools load there, the project is marked as seen.
Single-page apps and client-side routing
ClickNote works with React, Next and Vue routers. The review tools stay loaded while the app changes screens without a reload, and they read the address again on every change, so each note is filed under the screen it was left on and each screen shows its own pins. When a screen is redrawn, a pin finds its element again by selector, then by XPath, then by a fingerprint of its text.
What a note holds, and what it never holds
- The address of the screen and the element’s CSS selector and XPath.
- The element’s text and a snippet of its HTML. If someone clicks a table cell with a customer’s name in it, that name is in the note.
- The browser, operating system, viewport and layout.
- A screenshot of the area around the element, or of what was on screen for a note about the whole page. It shows what the reviewer could see, so on a dashboard it can include real data.
Values typed into form fields are never captured. Text boxes, text areas and drop-downs are blanked before a screenshot is taken, and a field’s value attribute is stripped from the HTML that is kept.
Where a picture of the screen is more than you want stored, switch screenshots off for the project under Review tools. The review tools then capture no picture, and ClickNote refuses one if it is sent. A workspace’s owner can make that the starting point for every new project.
Where it falls short behind a login
- A reviewer needs their own way in. ClickNote shares feedback, not access. Someone without an account in your app cannot review its signed-in screens.
- A pin is only as visible as the screen. To see a note in place, a developer opens that address signed in as someone who can reach it. If a screen shows different data to different people, the element may not be there for them; the screenshot and the HTML in the note show what the reviewer saw.
- Screens inside an iframe are not covered. The snippet stands down when the page is framed inside another page.
- A screenshot can fail. The browser builds it from the page, and some pages, such as ones with pictures from another origin that it may not read, leave it with nothing to send. The note is saved without one.
- No session recording, console log or network log. A note says what was clicked and what it looked like, not what the app did before that.
- Web only. ClickNote works in a browser. It does not review native mobile or desktop apps, APIs or server code.
Who reviews, and who fixes
Product managers, designers, support staff and customers in a pilot can all review through the same link, free. The notes land in one dashboard with statuses and threads, and an AI coding agent can read them over MCP. See feedback from product managers to developers and UI and UX review on the built site.