Stanki Guild

Confluence app

Attestation Flow for Confluence: know who has read and understood each version of a Confluence page

Ask named people to confirm a page, and keep a receipt tied to the exact version they read.

View on the Atlassian Marketplace

Who it is for

#
  • Policy owners, compliance and security leads who publish policies and procedures in Confluence.
  • Team leads who need to know that everyone has read a runbook or a change in how work is done.
  • Teams preparing evidence of acknowledged policies for an audit such as ISO 27001.

What it does

#
  • Receipts bound to the page version. Each confirmation is a receipt for the exact version that was read. After an edit, readers are asked again and earlier receipts stay as history.
  • Named readers and due dates. Choose readers with the people picker and set a due date. Confluence groups and a re-acknowledgement window are in the paid edition.
  • A signature record. Each receipt keeps the name at signing and a SHA-256 checksum of the version that was acknowledged. The page body itself is not stored.
  • Quizzes, reading time and a PIN (paid). Ask questions before the confirm button works, set a minimum reading time, and require a signature PIN.
  • Reports and evidence (paid). A compliance report with CSV, Excel and PDF export, an acknowledgement certificate and an audit evidence pack show who has and has not acknowledged.
  • Reminders and escalation (paid). Reminder comments and escalation of overdue acknowledgements are posted on the page where you turn them on.
  • Approval before reading (paid). Approvers sign off each version, or one section of a page, before readers are asked. The author of a version cannot approve it, and an optional review stage and revision labels (Rev 01, Rev A) are available.
  • Attachments, courses and permissions. Readers can acknowledge a page's attachments by file version and checksum (paid), work through ordered courses (paid), and sign with a PIN or an authenticator app (paid). A Permissions tab sets who may relax a control or see names in reports; its built-in roles work in every edition and editing them is paid.

Every feature is described in the documentation. Features marked paid need a paid licence; sites with up to 10 users get every feature free.

How it works

#
  1. On the page, click Require acknowledgement, choose the required readers and set a due date.
  2. Readers confirm with one button. Each confirmation becomes a receipt for that page version.
  3. Check who is outstanding in the report. When the page changes, readers are asked to confirm the new version.

Product video

#

A short product video will be shown here. It is not recorded for the website yet.

Pricing and installation

#

Install it from the Atlassian Marketplace listing (Attestation Flow: Read Confirmations for Confluence). Billing, trials and licences are handled by Atlassian.

Free, with every feature, for sites with up to 10 users. Prices above that are on the pricing page and on the Marketplace listing.

Security and your data

#

Attestation Flow for Confluence is an Atlassian Forge app. It has no Forge remote, no web trigger and no calls to external hosts. Its records are kept in Forge hosted storage on your own Atlassian site and follow Atlassian's data-residency arrangements for that site. We run no servers for the apps and use no sub-processors. Details: Security Policy, Privacy Policy, Data Processing Addendum.

Documentation and support

#