Read confirmations for Confluence, sealed to the version each person read
Some pages must not only be published: they must be read, and you must be able to prove it. ReadSeal turns that into a campaign, and keeps the evidence inside Confluence.
What it does. Pick the pages, by label, page tree, list or whole space. Pick who must confirm: named people or Confluence groups. Set a due date. Each reader sees a counter under the page title and an "I have read it" button, with an attestation text to tick if you wrote one.
What makes it evidence. Every confirmation records the exact page version. A republished page asks again and keeps the earlier confirmation. A click on a page that changed while it was being read is refused. Identity comes from Atlassian, never from the browser.
What your auditor opens. A campaign page written by ReadSeal in Confluence, filed in a register for the space: who confirmed what and when, a task per person, a CSV report, and a final sealed version when you close the campaign.
Where to start
- Documentation: install it, run your first campaign, and what every screen means.
- FAQ: the questions people ask before buying.
- Security: what the app stores, where, and what it never does.
- Privacy policy.
- Support: how to reach a human.
Good to know
- ReadSeal runs entirely on Atlassian: no external server, no email sent by the app, no tracking.
- The app speaks English, French, Spanish and German, and follows each reader's language.
- The evidence is a Confluence page: it stays with you, and it survives the app being uninstalled.