AccessLedgerBack to the overview

An example evidence record

Q3 2026 user access review at Harbourline Logistics, closed and sealed.

This is an example of the record the app produces. This is a real run of the product pipeline over a fictional tenant. The company, people, projects and spaces are invented; the findings, the permission chains and the digest are computed, not written by hand.

Written by accessledger sample generator. Everything below is rendered straight from the artifact — the same file, unedited.

Both products. One round. One signature.

Jira Cloud

19

grants reviewed across 19 projects

Confluence Cloud

22

grants reviewed across 8 pages and 14 spaces

Sealed together

1

SHA-256 digest over all 41 grants, signed off by one reviewer on one date

An access review covers every system in scope, and Jira and Confluence are almost always both in scope for the same company. The competing Marketplace apps each cover one of them, so the best they can produce is two records that do not join — and two records that do not join is two half-answers. Everything on this page is one round, under one hash.

What the scan surfaced

Findings are computed from the same snapshot the round was opened against. Each one names the evidence it rests on, so a reviewer can check it rather than take it on trust.

  • DEACTIVATED_USER_WITH_ACCESS

    Deactivated account still has access to ENG

    critical

    Jo Whitfield is deactivated in Atlassian but still resolves to 1 permission(s) on project ENG.

    Evidence

    • Jo Whitfield (557058:a1c4e2f0-5555-4a01-9c31-0b6d21f4a005)
    • project ENG
    • BROWSE_PROJECTS

  • VIEW_RESTRICTED_BUT_EDITABLE

    Page "Q3 Board Pack" looks restricted, but everyone who can view it can also edit it

    high

    Page "Q3 Board Pack" (p-board-q3) in space BOARD "Board" carries a view restriction, so it displays as locked. All 1 user who can view it can also edit it — no edit restriction is set on the page, so editing falls back to the space update grant. (Site and space administrators are excluded from that count; they can view and edit regardless.) View restrictions cascade to child pages in Confluence; edit restrictions do not, so an edit restriction on an ancestor does not protect this page.

    Evidence

    • View restriction on ancestor page "Board Space Home" (p-board-root): group "platform-admins" (2 members).
    • Effective viewers, excluding administrators: Tomas Lindqvist (557058:a1c4e2f0-2222-4a01-9c31-0b6d21f4a002).
    • NO edit restriction is set on this page, so editing falls back to the space BOARD "update" permission (group "platform-admins" (2 members)). View gates edit, so that grant narrows to the view audience — and it does not narrow it further, which leaves every viewer able to edit.
    • Effective editors, excluding administrators: Tomas Lindqvist (557058:a1c4e2f0-2222-4a01-9c31-0b6d21f4a002).
    • Site administrators view and edit every space regardless of page restrictions (via global:ADMINISTER): Priya Raman (557058:a1c4e2f0-1111-4a01-9c31-0b6d21f4a001).

  • VIEW_RESTRICTED_BUT_EDITABLE

    Page "Board Space Home" is editable by everyone who can view it, which appears deliberate

    low

    Page "Board Space Home" (p-board-root) in space BOARD "Board" carries a view restriction and its own edit restriction, and the two cover the same people. All 1 user who can view it can also edit it. (Site and space administrators are excluded from that count; they can view and edit regardless.) An edit restriction was set on this page explicitly, so this reads as a deliberate choice rather than the cascade gap, and is recorded at low severity for completeness.

    Evidence

    • View restriction on this page "Board Space Home" (p-board-root): group "platform-admins" (2 members).
    • Effective viewers, excluding administrators: Tomas Lindqvist (557058:a1c4e2f0-2222-4a01-9c31-0b6d21f4a002).
    • An edit restriction IS set on this page (group "platform-admins" (2 members)), and it names the same people as the view audience, so it does not narrow anything. Because the restriction was set explicitly, this looks like a deliberate configuration rather than the inheritance gap, and is recorded at low severity.
    • Effective editors, excluding administrators: Tomas Lindqvist (557058:a1c4e2f0-2222-4a01-9c31-0b6d21f4a002).
    • Site administrators view and edit every space regardless of page restrictions (via global:ADMINISTER): Priya Raman (557058:a1c4e2f0-1111-4a01-9c31-0b6d21f4a001).

The round, and who signed it off

Organisation
Harbourline Logistics
Atlassian site
harbourline.atlassian.net
Round identifier
round-2026-q3
Framework this evidence is kept for
SOC 2
Permissions snapshotted
14 Aug 2026, 09:00 UTC
Opened, then closed
14 Aug 2026 — 18 Aug 2026, 14:44 UTC
Decisions
39 approved · 1 revoked · 1 exceptions
Undecided at close
0 — a round cannot close while any item is open
Findings raised
3

  • Priya Raman

    Head of Security

    Scope
    All Jira projects and Confluence spaces
    Items reviewed
    41
    Atlassian account
    557058:a1c4e2f0-1111-4a01-9c31-0b6d21f4a001

Every grant, and what made it true

The chain under each permission is the part the native admin screens do not give you. It reads outermost first: the permission scheme, then the project role, then the group, then the direct grant — or a site-wide permission that overrides every scheme. Permissions are shown as Atlassian names them, because being exact about what a grant allows is the point.

Jira Cloud

19 grants across 19 projects

  1. Jira project ENG

    Priya Raman

    Approved

    ADMINISTER_PROJECTS

    global:ADMINISTER

    557058:a1c4e2f0-1111-4a01-9c31-0b6d21f4a001 · decided 18 Aug 2026, 14:31 UTC

  2. Jira project ENG

    Priya Raman

    Approved

    BROWSE_PROJECTS

    global:ADMINISTER

    557058:a1c4e2f0-1111-4a01-9c31-0b6d21f4a001 · decided 18 Aug 2026, 14:31 UTC

  3. Jira project ENG

    Priya Raman

    Approved

    EDIT_ISSUES

    global:ADMINISTER

    557058:a1c4e2f0-1111-4a01-9c31-0b6d21f4a001 · decided 18 Aug 2026, 14:31 UTC

  4. Jira project SUP

    Priya Raman

    Approved

    ADMINISTER_PROJECTS

    global:ADMINISTER

    557058:a1c4e2f0-1111-4a01-9c31-0b6d21f4a001 · decided 18 Aug 2026, 14:31 UTC

  5. Jira project SUP

    Priya Raman

    Approved

    BROWSE_PROJECTS

    global:ADMINISTER

    557058:a1c4e2f0-1111-4a01-9c31-0b6d21f4a001 · decided 18 Aug 2026, 14:31 UTC

  6. Jira project SUP

    Priya Raman

    Approved

    EDIT_ISSUES

    global:ADMINISTER

    557058:a1c4e2f0-1111-4a01-9c31-0b6d21f4a001 · decided 18 Aug 2026, 14:31 UTC

  7. Jira project ENG

    Tomas Lindqvist

    Approved

    ADMINISTER_PROJECTS

    scheme:Engineering Defaultgroup:platform-admins

    557058:a1c4e2f0-2222-4a01-9c31-0b6d21f4a002 · decided 18 Aug 2026, 14:31 UTC

  8. Jira project ENG

    Tomas Lindqvist

    Approved

    BROWSE_PROJECTS

    scheme:Engineering Defaultgroup:engineering

    557058:a1c4e2f0-2222-4a01-9c31-0b6d21f4a002 · decided 18 Aug 2026, 14:31 UTC

  9. Jira project ENG

    Tomas Lindqvist

    Approved

    EDIT_ISSUES

    scheme:Engineering Defaultrole:Developersgroup:engineering

    557058:a1c4e2f0-2222-4a01-9c31-0b6d21f4a002 · decided 18 Aug 2026, 14:31 UTC

  10. Jira project SUP

    Tomas Lindqvist

    Approved

    BROWSE_PROJECTS

    scheme:Support Defaultgroup:engineering

    557058:a1c4e2f0-2222-4a01-9c31-0b6d21f4a002 · decided 18 Aug 2026, 14:31 UTC

  11. Jira project ENG

    Ana Duarte

    Approved

    BROWSE_PROJECTS

    scheme:Engineering Defaultgroup:engineering

    557058:a1c4e2f0-3333-4a01-9c31-0b6d21f4a003 · decided 18 Aug 2026, 14:31 UTC

  12. Jira project ENG

    Ana Duarte

    Approved

    EDIT_ISSUES

    scheme:Engineering Defaultrole:Developersgroup:engineering

    557058:a1c4e2f0-3333-4a01-9c31-0b6d21f4a003 · decided 18 Aug 2026, 14:31 UTC

  13. Jira project SUP

    Ana Duarte

    Approved

    ADMINISTER_PROJECTS

    scheme:Support DefaultprojectLead

    557058:a1c4e2f0-3333-4a01-9c31-0b6d21f4a003 · decided 18 Aug 2026, 14:31 UTC

  14. Jira project SUP

    Ana Duarte

    Approved

    BROWSE_PROJECTS

    scheme:Support Defaultgroup:engineering

    557058:a1c4e2f0-3333-4a01-9c31-0b6d21f4a003 · decided 18 Aug 2026, 14:31 UTC

  15. Jira project ENG

    Marcus Bell

    Approved

    BROWSE_PROJECTS

    scheme:Engineering Defaultgroup:engineering

    557058:a1c4e2f0-4444-4a01-9c31-0b6d21f4a004 · decided 18 Aug 2026, 14:31 UTC

  16. Jira project ENG

    Marcus Bell

    Approved

    EDIT_ISSUES

    scheme:Engineering Defaultrole:Developersgroup:engineering

    557058:a1c4e2f0-4444-4a01-9c31-0b6d21f4a004 · decided 18 Aug 2026, 14:31 UTC

  17. Jira project SUP

    Marcus Bell

    Approved

    BROWSE_PROJECTS

    scheme:Support Defaultgroup:engineering

    557058:a1c4e2f0-4444-4a01-9c31-0b6d21f4a004 · decided 18 Aug 2026, 14:31 UTC

  18. Jira project ENG

    Jo Whitfield

    Revoked

    BROWSE_PROJECTS

    scheme:Engineering Defaultgroup:contractors-2024

    557058:a1c4e2f0-5555-4a01-9c31-0b6d21f4a005 · decided 18 Aug 2026, 14:31 UTC

  19. Jira project ENG

    Release Bot

    Exception

    EDIT_ISSUES

    scheme:Engineering Defaultgroup:release-automation

    Reviewer’s written reason

    Service account for the release pipeline. Credentials rotate every 90 days and it cannot log in interactively. Reviewed with the platform lead.

    557058:a1c4e2f0-6666-4a01-9c31-0b6d21f4a006 · decided 18 Aug 2026, 14:31 UTC

Confluence Cloud

22 grants across 8 pages and 14 spaces

  1. Confluence page p-board-q3

    Priya Raman

    Approved

    read

    global:ADMINISTERpage:p-board-root:viewgroup:platform-admins

    557058:a1c4e2f0-1111-4a01-9c31-0b6d21f4a001 · decided 18 Aug 2026, 14:31 UTC

  2. Confluence page p-board-q3

    Priya Raman

    Approved

    update

    global:ADMINISTERpage:p-board-root:viewgroup:platform-adminsspace:BOARD:updategroup:platform-admins

    557058:a1c4e2f0-1111-4a01-9c31-0b6d21f4a001 · decided 18 Aug 2026, 14:31 UTC

  3. Confluence page p-board-root

    Priya Raman

    Approved

    read

    global:ADMINISTERpage:p-board-root:viewgroup:platform-admins

    557058:a1c4e2f0-1111-4a01-9c31-0b6d21f4a001 · decided 18 Aug 2026, 14:31 UTC

  4. Confluence page p-board-root

    Priya Raman

    Approved

    update

    global:ADMINISTERpage:p-board-root:viewgroup:platform-adminspage:p-board-root:editgroup:platform-admins

    557058:a1c4e2f0-1111-4a01-9c31-0b6d21f4a001 · decided 18 Aug 2026, 14:31 UTC

  5. Confluence space BOARD

    Priya Raman

    Approved

    administer

    global:ADMINISTER

    557058:a1c4e2f0-1111-4a01-9c31-0b6d21f4a001 · decided 18 Aug 2026, 14:31 UTC

  6. Confluence space BOARD

    Priya Raman

    Approved

    read

    global:ADMINISTERspace:BOARD:readgroup:platform-admins

    557058:a1c4e2f0-1111-4a01-9c31-0b6d21f4a001 · decided 18 Aug 2026, 14:31 UTC

  7. Confluence space BOARD

    Priya Raman

    Approved

    update

    global:ADMINISTERspace:BOARD:updategroup:platform-admins

    557058:a1c4e2f0-1111-4a01-9c31-0b6d21f4a001 · decided 18 Aug 2026, 14:31 UTC

  8. Confluence space ENG

    Priya Raman

    Approved

    administer

    global:ADMINISTERspace:ENG:administeruser:557058:a1c4e2f0-1111-4a01-9c31-0b6d21f4a001

    557058:a1c4e2f0-1111-4a01-9c31-0b6d21f4a001 · decided 18 Aug 2026, 14:31 UTC

  9. Confluence space ENG

    Priya Raman

    Approved

    read

    global:ADMINISTER

    557058:a1c4e2f0-1111-4a01-9c31-0b6d21f4a001 · decided 18 Aug 2026, 14:31 UTC

  10. Confluence space ENG

    Priya Raman

    Approved

    update

    global:ADMINISTER

    557058:a1c4e2f0-1111-4a01-9c31-0b6d21f4a001 · decided 18 Aug 2026, 14:31 UTC

  11. Confluence page p-board-q3

    Tomas Lindqvist

    Approved

    read

    page:p-board-root:viewgroup:platform-admins

    557058:a1c4e2f0-2222-4a01-9c31-0b6d21f4a002 · decided 18 Aug 2026, 14:31 UTC

  12. Confluence page p-board-q3

    Tomas Lindqvist

    Approved

    update

    page:p-board-root:viewgroup:platform-adminsspace:BOARD:updategroup:platform-admins

    557058:a1c4e2f0-2222-4a01-9c31-0b6d21f4a002 · decided 18 Aug 2026, 14:31 UTC

  13. Confluence page p-board-root

    Tomas Lindqvist

    Approved

    read

    page:p-board-root:viewgroup:platform-admins

    557058:a1c4e2f0-2222-4a01-9c31-0b6d21f4a002 · decided 18 Aug 2026, 14:31 UTC

  14. Confluence page p-board-root

    Tomas Lindqvist

    Approved

    update

    page:p-board-root:viewgroup:platform-adminspage:p-board-root:editgroup:platform-admins

    557058:a1c4e2f0-2222-4a01-9c31-0b6d21f4a002 · decided 18 Aug 2026, 14:31 UTC

  15. Confluence space BOARD

    Tomas Lindqvist

    Approved

    read

    space:BOARD:readgroup:platform-admins

    557058:a1c4e2f0-2222-4a01-9c31-0b6d21f4a002 · decided 18 Aug 2026, 14:31 UTC

  16. Confluence space BOARD

    Tomas Lindqvist

    Approved

    update

    space:BOARD:updategroup:platform-admins

    557058:a1c4e2f0-2222-4a01-9c31-0b6d21f4a002 · decided 18 Aug 2026, 14:31 UTC

  17. Confluence space ENG

    Tomas Lindqvist

    Approved

    read

    space:ENG:readgroup:engineering

    557058:a1c4e2f0-2222-4a01-9c31-0b6d21f4a002 · decided 18 Aug 2026, 14:31 UTC

  18. Confluence space ENG

    Tomas Lindqvist

    Approved

    update

    space:ENG:updategroup:engineering

    557058:a1c4e2f0-2222-4a01-9c31-0b6d21f4a002 · decided 18 Aug 2026, 14:31 UTC

  19. Confluence space ENG

    Ana Duarte

    Approved

    read

    space:ENG:readgroup:engineering

    557058:a1c4e2f0-3333-4a01-9c31-0b6d21f4a003 · decided 18 Aug 2026, 14:31 UTC

  20. Confluence space ENG

    Ana Duarte

    Approved

    update

    space:ENG:updategroup:engineering

    557058:a1c4e2f0-3333-4a01-9c31-0b6d21f4a003 · decided 18 Aug 2026, 14:31 UTC

  21. Confluence space ENG

    Marcus Bell

    Approved

    read

    space:ENG:readgroup:engineering

    557058:a1c4e2f0-4444-4a01-9c31-0b6d21f4a004 · decided 18 Aug 2026, 14:31 UTC

  22. Confluence space ENG

    Marcus Bell

    Approved

    update

    space:ENG:updategroup:engineering

    557058:a1c4e2f0-4444-4a01-9c31-0b6d21f4a004 · decided 18 Aug 2026, 14:31 UTC

The seal

When the round closed, all 41 grants above — Jira Cloud and Confluence Cloud together — were serialised in a fixed field order with items sorted by key, and hashed with SHA-256. Change one decision, one timestamp or one reviewer and the digest no longer matches, which is what makes the record tamper-evident rather than merely dated. The round is also immutable once closed: the engine refuses to record a further decision against it.

sha-256:75acfb927802ddab289299a231908940d4fe53d64b3a523bc5a7a65ee151c4a2

The organisation name, the period label and the reviewer job titles on this page sit outside that hash on purpose. Who decided what is already attested per grant and is covered by the digest; a job title is presentation, and folding it in would mean a copy-edit invalidated the evidence.

That is the whole product

A permission report you could regenerate tomorrow. A record of who reviewed it, and when, that you could not.

Back to the overview