is reachable two ways: in-app via reviewer.php?_action=adgreeRev (also auto-selected whenever a t or _ad query parameter is present), and pre-login via an emailed encrypted link (reviewer.php?_ad=...) that auto-authenticates the reviewer through loginReviewersA(). The same accept/decline choice is also offered inline inside the New Reviewer Invitation row's preview modal (previewManuscript, review_st=new) — both paths write to the same acceptRejectManuscript() logic, so this is one row, not two.

has no ?_action= of its own — it is the previewManuscript/showEvaluationForm modal (loaded via request/reviewer.ajax.php, task=showManusriptDetails) opened by clicking a row in Pending Assignments. It is counted as its own row per the row-identification method's "distinct tab/sub-view within an action" clause, since it renders a materially different screen (the scored evaluation form with file upload) from the list it is launched from.

: the rv=<manu_rev_code> query parameter (FUNCTION=rvCertManu) renders a distinct single-manuscript certificate, reached only via a per-row certificate icon link on Completed Assignments — separate from the aggregate, multi-manuscript certificate produced by the base cert action's search form/result.

— the base, no-rvc screen — is not linked from any menu or view in this module: tracing its SQL shows a hardcoded 2020-05-19..2021-03-12 date range, i.e. it is a leftover, journal-wide incident tool built for a specific OVH data-center fire, reachable only by typing the URL directly. Its sibling _action=pbl (save to Publons) is even more clearly dead: reviewer.php calls $cnf->publonsReviewSave(), but no such method is defined anywhere in the codebase — it would fatal-error if ever hit, so it is not listed as a row (renders nothing).

(&rvc=..., reparirRvManuFileForm()) renders a materially different screen from its base sibling above — a single-manuscript file-picker/re-upload form scoped to one reviewer/manuscript-reviewer pair, versus the base tool's journal-wide mass-selection list plus TinyMCE email composer — so it is split out as its own row, the same way Get Review Certificate — Single Manuscript is split from the base certificate row above. Unlike its base sibling, it genuinely is linked: via a per-row upload icon rendered inside the base tool's own mass-selection table (repair.manu.files.class.php:560, href="reviewer?_action=repair&eic=1&rvc=..."), and via the emailed _ad-encrypted auto-login link, which redirects straight to this URL through ReparManuFiles::loginRvRepairLink() (repair.manu.files.class.php:796-821).

(_action=info) is a public page — it skips the role-3 auth check entirely and is linked from the journal's public navigation menu (menu_rev) as "Reviewers". Every other row in this table requires the Reviewer role; this one does not.

(journal/rev_questions.php, opened by inc/js/reviewer.js's own showRevNote(ID) loading ./journal/rev_questions?_rv=1&revNote=...) folds into the manuscript rows above rather than getting its own row — same shared partial documented in full at Editor-in-Chief (route-file checklist gap, resolved 2026-07-02).