Read Receipts for Confluence

You wrote the policy. Now prove people read it.

Every team has pages people must read — security policies, safety procedures, onboarding documents.

1. Require acknowledgement on a page, and name the people who must read it.

2. Readers confirm in one click from a banner. Identity and date are recorded.

3. The panel shows who has acknowledged and who hasn't — so you chase three people, not thirty.

An acknowledgement is written once with a server-side timestamp. It is never edited or overwritten, and survives the requirement being switched off and on. A reader can only acknowledge as themselves.

Your data stays in Atlassian. The app runs entirely on Forge and stores acknowledgements inside your own tenancy. It makes no outbound calls; its only permission is access to its own storage.

Configuration is per page today, and the panel lists the first 100 acknowledgements. Acknowledgement across a whole page tree is next on the roadmap — tell us and it moves faster.