Confirm on the page
People click the status under the title, read, answer the check questions and confirm a statement such as "I have read and understood this page".
Read and confirm for Confluence. Ask people or groups to read a policy, check they understood it with a few questions, and keep their confirmation tied to the version they read.
Readworthy puts a read-and-confirm campaign on any Confluence page. Everyone asked sees their own status under the title, answers the check questions and confirms. Edit the page and they're asked again. One report shows who is outstanding, and the CSV goes to your auditors.
People click the status under the title, read, answer the check questions and confirm a statement such as "I have read and understood this page".
Up to five multiple-choice questions. Answers are checked on the server, the right answers never reach the browser, and a wrong answer shows which questions to revisit.
A confirmation counts for the content it was given on. Edit the page and everyone is asked to confirm the new version. A title change doesn't count as a change.
Ask named people or Confluence groups, up to 1,000 people per page, with a due date. Refresh a group's members when people join.
When a campaign starts, Readworthy asks Confluence who among the people asked can't view the page, because of page restrictions or space permissions, and shows editors their names.
Keep only the result, the score and the time, never the answers. Open feedback is stored without a name.
Confirmations are stored in your own Atlassian site. Readworthy has no servers of its own and calls nothing outside Atlassian.
Readworthy is not on the Atlassian Marketplace yet. These steps apply once it is listed.
Readworthy works on pages. Blog posts aren't supported yet.
Each person sees their own status:
| Under the title | Meaning |
|---|---|
| Read & confirm | Nobody has been asked to confirm this page. |
| Please confirm by 20 Nov | You've been asked to read and confirm this page. |
| Please confirm again | You confirmed an earlier version, and the content has changed since. |
| You confirmed v7 | You've confirmed the current content. The number is the version you confirmed. |
| Confirmed by 12 of 40 | Shown to everyone else: how many of the people asked have confirmed the current content. |
Statuses are worked out every time the page is viewed. They refresh when the page loads.
Anyone who can edit the page can start a campaign. Click Read & confirm under the title and fill in:
| Field | Rules |
|---|---|
| People, Groups | Up to 25 people and groups. Group members are added when the campaign starts, up to 1,000 people per page. |
| Confirm by | Optional. Shown under the title and in the report, where overdue campaigns are highlighted. |
| What people confirm | The statement people confirm, up to 300 characters. The default is "I have read and understood this page." |
| Questions and pass mark | Optional, up to five (Add a question). Each has 2 to 6 answers, one per line, and a right answer. The pass mark is how many must be right; it defaults to all of them. |
| Open question for feedback | Optional, for feedback such as "Anything unclear?". Answering it is optional for readers. |
| Ask everyone again when the page's content changes | On by default. When the content changes, everyone has to confirm the new version. |
| Privacy mode | Off by default. When on, only pass or fail, the score and the time are kept, never the answers, and open feedback is stored without a name. |
| Tell people | On by default: posts a page comment that @mentions them. |
A page has one campaign at a time. When people join a group, select Update the group members in the dialog to add them.
When the campaign starts, and whenever you update the group members, Readworthy checks with Confluence that everyone asked can view the page. If some can't, the dialog names them, so you can fix the page restrictions or the space permissions and select Check again. Large audiences are checked in steps: select Check the rest to continue.
If the campaign has an open question, readers can answer it when they confirm. People who can edit the page see the answers in the Readworthy dialog under Feedback, newest first, with each reader's name.
In privacy mode the answers are kept without names and shown as Anonymous. They aren't in the CSV export, which is per person.
Readworthy doesn't send email itself. When a campaign starts it posts one page comment, as the person who started it, and Confluence notifies the people mentioned in the usual way.
Open Apps → Readworthy to see Waiting for you, the pages you still have to confirm, and every open campaign on pages you can view, with its space, progress, due date and start date. A campaign where some people can't view the page is marked, for example 5 can't view.
Export confirmations (CSV) lists every attempt, oldest first, including those of closed campaigns:
| Column | What it contains |
|---|---|
| time_utc | When it happened, in UTC |
| page_id, page_title, space_key | The page, as it is called now |
| page_version | The version that was confirmed |
| person, account_id | Who confirmed: their current Confluence name and Atlassian account ID |
| result, score | confirmed or not passed, and the score, such as 2/2 |
| campaign_id, campaign_started_utc, due_date | The campaign the attempt belongs to |
| feedback | The reader's answer to the open question (empty in privacy mode) |
The report and the export only include pages you can view in Confluence. Cells that would start a spreadsheet formula are prefixed with an apostrophe, so the file is safe to open in Excel.
Anyone who can edit the page can close its campaign from the dialog, for example to start a new one with different people. The page goes back to Read & confirm, and its confirmations stay in the CSV export.
| What | Where it lives | Who can see it |
|---|---|---|
| Campaigns: page ID and version, the people and groups asked, due date, statement, questions with their right answers, and the Atlassian account ID of the person who started it | Your Atlassian site's app storage (Forge storage) | People who can view the page see the progress; the right answers are never sent to the browser |
| Confirmations: person's Atlassian account ID, page version, time, pass or fail, score and, unless privacy mode is on, the answers and any open feedback | Your Atlassian site's app storage (Forge storage) | People who can view the page see who has confirmed; the CSV gives results and scores |
| The result of the view check: the Atlassian account IDs of people asked who can't view the page | Your Atlassian site's app storage (Forge storage) | People who can edit the page |
| Open feedback in privacy mode | Your Atlassian site's app storage, without a name | Nobody can tell who wrote it |
| Page content | Read as the viewing user to tell whether it changed since someone confirmed (a fingerprint of the content is stored, not the text) | Only people who can already see that page |
| The comment Readworthy posts | On the page, like any other Confluence comment, posted as the person who started the campaign | People who can view the page |
See also our privacy policy.
| Message or problem | What to do |
|---|---|
| "Only people who can edit this page can ask others to confirm it" | Ask someone with edit access to the page, or a space admin, to start the campaign. |
| "People have already been asked to confirm this page" | A page has one campaign at a time. Close it from the dialog, then start a new one. |
| "You haven't been asked to confirm this page" | Only the people asked can confirm. If you joined a group after the campaign started, ask the page's editor to select Update the group members. |
| "The page changed while you were reading it" | Reload the page, read the new version and confirm again. |
| "N of the people asked can't view this page" | Those people can't open the page, so they can't confirm it. Check the page's restrictions (the padlock on the Share button) and the space's permissions, then select Check again in the dialog. |
| "Readworthy couldn't check who can view this page" | Confluence didn't answer the check on this site. The campaign still works; people who can't view the page just won't see it. |
| "Only the first 1,000 people were included" | Readworthy asks up to 1,000 people per page. Split the audience across pages or use smaller groups. |
| Status still shows the old state | The status under the title refreshes when the page loads. Reload the page. |
| A page is missing from the report | The report only shows open campaigns on pages you can view. Closed campaigns are in the CSV export. |
| "Readworthy's licence for this site isn't active" | The subscription or trial has ended. A Confluence admin can renew it from the apps section of Atlassian Administration. Until then statuses, the report and the CSV export still work. |
| Confirmations are gone after reinstalling | Atlassian doesn't restore an app's data when it's reinstalled. Keep the CSV export from before uninstalling. A Confluence admin can ask us within 21 days of uninstalling to request a recovery from Atlassian. |
| Version | Date | Changes |
|---|---|---|
| 0.1.0 | 7 Nov 2026 | First version: read-and-confirm campaigns on pages with people and groups, check questions with a pass mark, version-bound confirmations, a check of who can't view the page, reader feedback for editors, privacy mode, @mention comment, report with Waiting for you, and CSV export. Not yet released. |
Email office@smarteduonline.co.uk with the subject Readworthy support. Please include:
yourcompany.atlassian.netUse of Readworthy is covered by our terms of use and privacy policy.