Read Confirmations for Confluence
Readers confirm they have read a policy or procedure; editors see who has, who has not, and export the list for audits.
Add read confirmations to policies, procedures and onboarding pages. Readers confirm with one click; editors see who has confirmed, who must confirm again and who has not, and download the list. Runs entirely on Atlassian.
What it does
- Report for editors: confirmed, confirm again, not yet
- Required readers by Confluence group, with a deadline
- Ask everyone to confirm again, or after every update
- CSV download with names, dates and page versions
Where it appears
- Macro in the Confluence editor: type /Read confirmation.
How to use it
- Edit the page, type /Read confirmation and choose the macro.
- Optionally enter a message, pick a group of required readers and set a deadline. Save and publish.
- Readers click the confirm button.
- As an editor of the page, open Show who has confirmed to see the report or download the CSV.
- After a change that matters, choose Ask everyone to confirm again.
Permissions
The app runs on Atlassian’s Forge platform and declares no permission to contact outside servers. It asks for these scopes:
| Scope | Why |
|---|---|
| storage:app | Keep confirmations in the app's storage on Atlassian's platform. |
| read:page:confluence | Read the page version that a reader confirms. |
| read:blogpost:confluence | The same for blog posts. |
| read:confluence-content.permission | Show the report only to people who can edit the page. |
| read:confluence-groups | List the members of the required group for the not-yet list. |
| read:confluence-user | Show names in the report instead of account ids. |
Data and privacy
- What the app stores
- Per confirmation: Atlassian account id, page id, page version and time. Per page: the version from which confirmations are requested again.
- Personal data
- Atlassian account ids. No names or e-mail addresses are stored; names are read live from Confluence when an editor opens the report.
- Logs
- Counts from the daily personal data check and error messages, without account ids.
- Where it lives
- In the app’s storage on Atlassian’s Forge platform, in the same data residency location as your Atlassian site. Nothing is copied to servers outside Atlassian. When the app is uninstalled, Atlassian deletes its storage under Atlassian’s data retention policy.
Details for all apps are in the privacy policy, including the data processing addendum.
Good to know
- The not-yet list covers one required group per macro.
- Anonymous readers cannot confirm.
Questions
No. A confirmation is always stored for the logged-in person.
When their Atlassian account is closed, the daily personal data check erases their confirmations, as Atlassian requires.
Only people who can edit the page. Confluence’s own permission is checked on every request.