File tickets by clicking the live page
Open a review session on your own site, pick the element that is wrong and file a ticket against it. Sessions are signed and valid for eight hours.
Pro · review sessions valid 8 h
A render of review mode on a staging checkout page: the ticket composer pinned to the marked Place order button. Type Bug, priority High, the sentence “Tabbing to this button shows no focus ring.”, a thumbnail of the captured element, and the target read back as #place-order.
How it works
1
Start a review session
From the panel, or with the start_review_session MCP tool, which returns the URL to open and when it expires.
2
Point at what is wrong
The element you pick is stored with the ticket as a sanitized DOM selection, not as a description of where it was.
3
File it into the same pipeline
Review tickets enter Received with the same evidence and the same board as every other report.
Design review without a spreadsheet
The picker names what you are pointing at — the selector, the box model, whether it is keyboard-focusable — so the note is written against the element instead of in a document nobody can map back to the DOM.
A render of review mode on a staging checkout page. A floating dark bar reads “Ana Ruiz”, then “Choose an element · Escape to cancel”, with the element picker switched on; the picker highlights the page’s Place order button in the box-model colours a browser inspector uses and prints its node line, its spacing and its accessibility role on a card above it.
Filed, then straight back to pointing
Sending leaves a receipt card on the element: its stage, its type, its priority and the id it got. The picker re-arms behind it, so a pass over a page is one sweep rather than eight round trips to the board.
A render of review mode on a staging checkout page: the receipt for ticket NT-253, still pinned to the Place order button. Chips read Received, Bug and High, above the sentence “Tabbing to this button shows no focus ring.” and the reviewer’s initial, with the picker already armed again behind it.
Exact behaviour
- Session
- HMAC-signed token, valid 8 hours
- Selection
- Sanitized DOM selection stored on the ticket
- Access
- Member or above starts a session; a self-serve door is optional per project
- Browsers
- Chromium, WebKit, Firefox; desktop and mobile
- Plan
- Pro
- MCP tool
- start_review_session · create_ticket
Works with
Questions teams ask before installing
How long does a review session last?
Eight hours. The URL carries an HMAC-signed token that expires after that, and starting another session is one action.
Do reviewers need a Notarus account?
A member or above starts the session. Whether people without an account can open one themselves is a per-project setting.
Is review mode on the Free plan?
No. It is Pro, together with screen recording, integrations, exports, AI enrichment, custom CSS and whitelabel.
Review your next release on the page itself.
Review mode is part of Pro, at $29/month or $276/year.