Aldorock apps for Atlassian

Read Confirmations for Confluence

Ask the people who must read a page to confirm that they have. See who has and who has not, remind them with one click, and export the proof.

Getting started

  1. Install Read Confirmations for Confluence from the Atlassian Marketplace. Every page gets a Read confirmation entry under its title (the byline), every page's "…" menu gets Request read confirmations, and Read confirmations appears under Apps and in every space's apps.
  2. Request. Open the page, choose Request read confirmations from the "…" menu (under Apps), pick groups and people, set an optional due date, decide whether a changed page must be confirmed again, and whether people must re-read it every 3, 6, 12 or 24 months.
  3. Confirm. People who were asked see Confirm you have read this under the page title. They click it and press I have read this page. After that the byline reads You confirmed reading this.
  4. Follow up. Under Apps → Read confirmations, the requester, space admins and Confluence admins see every request with confirmed, open and overdue counts; open one to see each person. Remind by comment posts one comment on the page that mentions everyone still open, so Confluence notifies them. Export CSV downloads the audit list.

Who may do what

ActionWho
Request read confirmations on a pageAnyone who can edit the page, space admins, Confluence admins
ConfirmPeople in the request: named people and current members of the chosen groups
See who has and has not confirmed, remind, close, reopen, deleteThe requester, the space's admins, Confluence admins
See their own statusEveryone, under the page title and in Apps → Read confirmations → My confirmations

Groups and joiners

Group members are read when you send the request and again whenever the list is viewed, so people who join a group later are included and must confirm too. People who leave a group are shown as Left, keep their history, and are no longer counted or reminded. If a page is deleted, its requests show as "page deleted" in the overview and can be closed or deleted there. A request can cover up to 2,000 people and 50 groups; a page can carry up to 20 requests.

Changed pages and re-reads

With Ask again when the page changes, a confirmation records the page version it was given for; when a newer version is published the person's status becomes Confirm again and the byline asks them once more. Note that any published edit counts, including a title-only change, because Confluence bumps the page version for it; turn the option off for pages that are edited often for cosmetic reasons. With a re-read interval, the status turns to Confirm again that many months after the last confirmation. The overview and the CSV show the reason.

Statuses

Due dates are calendar days ending at midnight UTC. Not yet: asked, not confirmed, no due date passed. Overdue: not confirmed and the due date has passed. Confirm again: confirmed earlier, but the page changed or the re-read is due. Confirmed: the confirmation stands.

Reminders

The app sends no email of its own. Remind by comment posts one footer comment on the page, written as the app, that mentions up to 100 people who still have to confirm; Confluence then notifies them the way it notifies any mention. It can be used once per request per day. Beyond that, share the page as you normally would.

Export

Export CSV from the overview downloads one row per person per request: space, page, requested by, due date, person, status, confirmed at, page version and reason. Values that start with a formula character are neutralised for spreadsheets.

Data and privacy

Requests and confirmations are stored in Forge storage inside your Atlassian site's region: page ids and titles, group names, the Atlassian account ids and display names of the people involved, times and page versions. Nothing leaves Atlassian. Deleting a request deletes its confirmations. See Privacy.

Limits

Guides

Changelog