Vouchline by RETEKHow reviewers are assigned, and what they can see
Who reviews what
When a review is created, every finding becomes an item assigned to exactly one person:
| Finding is about | Assigned to |
|---|---|
| a single project | the lead of that project |
| a single project whose lead cannot review | the review owner |
| something not tied to one project (a group, a permission scheme, a site-wide grant) | the review owner |
The review owner is the Jira administrator who created the review.
A project lead cannot review when the account is inactive, has no access to a Jira product, or is an app account. In that case the item goes to the review owner and the reason is recorded.
The assignment reason is stored with each item. The reviewer sees it on the item, and it is printed in the report and exported in Items (CSV).
Assignments are fixed when the review is created. Items cannot be reassigned in this version.
When the lead would review their own access
If a project lead is also the subject of a finding in that project, Vouchline reports this as a separate finding (rule R6, segregation of duties) so the conflict is visible to the auditor rather than hidden in the assignment.
What a reviewer decides
For each item the reviewer chooses one of three decisions and must write a justification — for approvals too:
- Approve access — the access is justified and stays.
- To revoke — the access is not justified. Vouchline records the decision; the permission is removed in Jira by an administrator.
- Defer — a decision is not possible yet. The item returns in the next review, marked as coming back.
A reviewer can change a decision while the review is open. The earlier decision is not erased: the change is written as a new link in the register, and the report marks the item as amended.
A reviewer can apply one decision and one justification to all items currently shown. Each item still gets its own link in the register.
Notifying reviewers
Vouchline sends no email and calls no webhook — nothing leaves your Atlassian site. After creating a review, the administrator gets a ready-to-paste message listing who was assigned how many items and where to find them (Jira → Apps → Vouchline).
Closing
Only an administrator can close a review, and closing is final: afterwards nobody — reviewer or administrator — can change a decision. Items left without a decision are recorded as unresolved and shown that way in the report.
Who can see what
| Screen | Who can open it | What it shows |
|---|---|---|
| Vouchline administration (Jira settings → Apps) | Jira administrators | scans, snapshots, all reviews, evidence packages, rules and settings |
| Vouchline (Apps menu) | any user who has items assigned | only that user's own items |
Three things enforce this:
- Jira restricts the administration screen to administrators, and every administrative operation of the app checks again, on the server, that the caller is a Jira administrator. The check is made on behalf of the calling user, not on behalf of the app.
- The reviewer's identity comes from Atlassian, never from the browser. The app takes the account from the Forge context of the request; a value sent by the page is ignored.
- Items are stored per reviewer. A reviewer's request can only address their own items; another reviewer's items are not reachable from it.
A reviewer who is not an administrator sees no snapshots, no other reviewers' items and no evidence packages.