Start free

Let reporters follow a bug without an account

The reporter portal hands the person who filed a bug a link to their own reports, and the stage each one is at. No account, no password, no seat on your plan.

Start free See the exact behaviour

Included on every plan

A signed per-reporter link: no account, no seat, every ticket that person filed

Status changes and public replies appear as the board moves

How it works

  1. 01

    Issue the link

    A reporter link comes from a ticket's menu in the panel, or from the create_reporter_portal_link MCP tool. It is signed, scoped to that person's reports on that project, and it expires in 30 days.

  2. 02

    They open it

    No password and no seat. The link carries its own proof, so there is nothing for the reporter to remember and nothing for you to send twice.

  3. 03

    They watch it progress

    Status changes and public replies appear on the same page, so nobody has to write “any update?” again.

What your team sees, and what the reporter does not

Your side of the same report is the whole evidence bundle: the annotated screenshot, the recording, the console and network cluster, the environment. Only the comments explicitly marked visible cross to the portal, and that split is a predicate in the query rather than a filter in the interface. Whether the screenshot and the recording travel with them is a switch, per project.

The status they read is the column you moved it to

There is nothing to copy across and nothing to keep in step. The reporter's page shows the stage the ticket is in on your board, in the project's own language, the moment it moves.

Exact behaviour

Access
A signed link, issued per project and reporter, valid for 30 days
Shows
Every ticket that person filed with this project, and the public replies on them
Privacy
Internal comments are never rendered; screenshots and recordings are a per-project switch
Language
English, Spanish, Portuguese, French or German, set per project
Plan
Every plan
MCP tool
create_reporter_portal_link · get_client_portal · set_client_portal

Works with

Client portal The other door: a named key for the client who pays. Board & pipeline Where the status the reporter sees comes from. Evidence capture What your team sees and the reporter does not.

Questions teams ask before installing

Does the reporter need a Notarus account?

No. The portal is a link scoped to that reporter's own tickets. Reporters never sign up and never occupy a seat on your plan.

Can reporters see internal comments?

No. Every comment is stored with a visibility, and the portal renders the ones marked visible to the client only.

What is the difference between this and the client portal?

Scope and credential. A reporter link is a signed token covering that one person's own reports, and it can only expire. A client access is a named row with its own key that sees the project's progress, and you can revoke or regenerate it whenever you like.

The thinking behind it

A notification outlives its permission Storing a notification freezes an access decision at write time. When the audience is a permission rather than a settled list, derive the feed on read.The bypass role is the one that proves nothing In most authorization functions the membership join also proves the resource exists. The branch that skips the join skips that proof, and the 404 with it.Reporter identity is a ladder, not a gate Recording where each part of a reporter's identity came from settles what to believe about a report. It never settles what that person is allowed to do.

Stop answering “any update?” by hand.

The reporter portal is included on the Free plan.

Start free See pricing
<script src="…/widget.js" data-key="pb_pub_…">