Vouchline by RETEKProve your Jira access reviews actually happened.
Vouchline scans Jira permissions, turns the risky findings into a review assigned to the right people, and records every decision in a hash-chained register. Your auditor can verify the result without trusting us.
Built on Atlassian Forge · read-only · no data leaves your Atlassian site
$ node verify-package.mjs vouchline-2026-10-11-package.json Vouchline evidence package — independent verification review Q4 2026 privileged access review site example.atlassian.net [ OK ] chain 7 links, each hash recomputed [ OK ] order numbered without a gap; closing link is last [ OK ] items 5 decided items match their last link [ OK ] closing closing totals equal the decisions before it [ OK ] seal data caveats and snapshot header match final chain hash b3e2870cbf6c46d6…2ab08bb2e51d RESULT: every check passed
From permissions to evidence in four steps
One periodic review, start to finish, inside Jira.
Scan
Vouchline reads the permission model of your site and stores it as a snapshot with a checksum. Read-only, on demand or on a schedule.
Find
Fourteen rules turn the snapshot into findings: privileged permissions for everyone, deactivated accounts with access, administrators, leads reviewing themselves.
Decide
Each finding goes to a named reviewer, with the reason. They approve, mark for revocation or defer — and must write why, approvals included.
Prove
Close the review and download the evidence package: a PDF report, two CSV files and a JSON package that can be verified independently.
Why it holds up in an audit
A tool that says about itself “the data is consistent” is not evidence. Vouchline is built so that you do not have to take its word for it.
Evidence your auditor can check without us
Every decision is a link in a SHA-256 hash chain. The exported package contains each link in full, so anyone can recompute the chain with a short script that shares no code with the app.
Reviewers decide, and must say why
No decision is accepted without a written justification. A changed decision does not erase the earlier one: it is recorded as a new link, and the report marks the item as amended.
Closing a review is final
After closing, nobody — reviewer or administrator — can change a decision. Items left undecided are reported as unresolved, not hidden.
A register where every entry holds on to the one before it
Changing, removing or reordering any decision changes the final hash — the one printed in the report you downloaded when the review was closed.
The first link seals the snapshot and the caveats about its quality, so the data a review was built on cannot be swapped afterwards either. How to verify a package yourself →
What Vouchline reads — and what it never touches
An access review tool sees who can do what. It should not see anything else.
It reads
- Projects, project leads and project roles
- Permission schemes and what they grant
- Groups, their members and product access
- Which accounts administer the site or Jira
It does not
- Read work items, comments, attachments or worklogs
- Change anything in Jira — every scope is read-only
- Send data outside your Atlassian site — no servers of ours, no telemetry
- Store people’s names — account identifiers only
Mapped to ISO/IEC 27001:2022 and NIS2
Every finding carries the requirements it relates to — on screen, in the report and in the CSV export.
| Rule | What it reports | Requirements |
|---|---|---|
| R12 | Privileged permission granted to every user | ISO 27001 A.8.2, A.5.15 · NIS2 21(2)(i) · CIR 11.3 |
| R13 | Deactivated account that still holds access | ISO 27001 A.5.18, A.5.16 · NIS2 21(2)(i) · CIR 11.2 |
| R14 | Account holding site or Jira administration | ISO 27001 A.8.2, A.5.18 · NIS2 21(2)(i) · CIR 11.3 |
| R6 | Project lead who would review their own access | ISO 27001 A.5.3 · CIR 11.2 |
The mapping is an aid, not a certificate. Vouchline supports the evidence for these requirements; it does not make an organisation compliant with them. Which requirements apply to you is decided by your auditor. All fourteen rules →
Questions people ask first
Does Vouchline remove permissions?
No. It has no write access to Jira. “To revoke” is a recorded decision; an administrator removes the access in Jira, and the next review reports whether it is still in place.
How do reviewers find out they have something to review?
Vouchline sends no email and calls no webhook, because 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.
What happens to the evidence if we uninstall the app?
Everything you downloaded stays valid and verifiable. Data kept inside the app does not survive an uninstall, so download the package when you close each review. Details →
Who can see what?
Jira administrators see scans, reviews and evidence packages. A reviewer sees only the items assigned to them. How this is enforced →
Does it cover Confluence or other products?
No. Vouchline reviews access to Jira Cloud.
Make the next access review the last one you rebuild by hand.
Questions before you try it? Write to support@retek.app.