Paperlatch

Page approval and document sign-off for Confluence

Approvers approve or reject the exact page version they read. When the page is edited, it shows that it is no longer approved.

Page Approval & Document Sign-off for Confluence is in Atlassian Marketplace review. The listing link will appear here once it is approved.

How it works

1. Insert the Page Approval macro on a page.
2. Anyone who can edit the page chooses up to 20 approvers, and whether everyone must approve or one approval is enough.
3. Each approver opens the page and selects Approve, or Reject with a comment saying why.
4. The page shows who has approved, who rejected and why, and who has not decided yet.

Bound to the version

A decision applies to one page version: its title and body, identified by a SHA-256 hash. When the page is edited, earlier decisions stay on record and the page shows Changed since approval: which version was approved, and that the current one is not. If the page changes while an approver is deciding, the decision is refused and they are asked to reload. Attachments, comments and labels are not part of the approved content, and the app says so.

Approvers need only read access

An approver needs to be able to read the page, not edit it. The app checks this when approvers are chosen and refuses a person who cannot see the page. Every change to the approvers is kept, with who made it and when, and shown on the page — so an approver who rejected cannot be quietly removed.

One list of what is waiting

From the Apps menu, Page Approval shows the pages waiting for your decision and every page with approvers, with its status and who has not decided. Both export as CSV. Confluence administrators also see the full audit trail. Each page lists only what you are allowed to read.

A record that can be checked

Each decision records the person, the time, the page version and the content hash, and carries the hash of the decision before it on the same page. A page whose record has been altered or has a decision missing is marked Record has problems. The check detects a change; it does not prevent one.

What it does not do

• It does not lock the page. Editing is not blocked; the edit is shown.
• It does not send email or notifications. Approvers see what is waiting for them on the app's page.
• It is not a regulated electronic signature (no signing PIN, no approved list of signers).

Read-only, on Atlassian Forge

The app reads pages, users and content permissions, and keeps its records in Atlassian's app storage inside your site. It does not write to your Confluence, does not act on a user's behalf, and never reads or stores email addresses. There is no server of ours. See the privacy policy for exactly what is stored.