Page sign-off for Confluence that auditors can trust. Each approval is tied to the exact version that was approved, and shows "Changed since approval" the moment the content changes.
Ask named people or Confluence groups to approve a page. Signworthy shows the page's approval status under its title, notifies approvers through Confluence itself, and keeps every request, approval and rejection, with the page version it applied to, in an audit trail you can export.
An approval counts for the content that was approved. Edit the page and its status changes to "Changed since approval" straight away. A new version with the same content, such as a title change or a restore, keeps the approval.
Readers see at a glance whether a page is approved, in review, changed or rejected, without opening anything.
Ask named people or Confluence groups, and decide whether everyone must approve or any number of them. Each person counts once, so two approvals always means two people.
Requests and outcomes are posted as page comments that @mention the right people, so Confluence's own notifications and emails do the rest.
Every request, approval, rejection and withdrawal, with the page version, the person and the time, exports as CSV from one report covering every space you can see.
Approvals are stored in your own Atlassian site. Signworthy has no servers of its own and calls nothing outside Atlassian.
Signworthy is not on the Atlassian Marketplace yet. These steps apply once it is listed.
Signworthy works on pages. Blog posts aren't supported yet.
| Under the title | Meaning |
|---|---|
| Approval | No approval has been requested for this page. |
| In review: 1 of 2 | Approval has been requested for the current version. The numbers show approvals so far and approvals needed. |
| Approved v12 | The approval rule is met for the content you're reading. The version is the one that was approved. |
| Changed since approval | An earlier version was approved, but the content has changed since. The approvers need to look at the current version. |
| Rejected | An approver rejected the current version and gave a reason. Click the status to read it. |
Statuses are worked out every time the page is viewed, by comparing the approved content with the page as it is now. They don't wait for a background job.
Anyone who can edit the page can request approval. Click Approval under the title and fill in:
| Field | Rules |
|---|---|
| People | Named approvers. Each of them has to approve (or count towards the number needed). |
| Groups | Confluence groups. Any one member's approval counts for the group. |
| Who has to approve | Everyone listed, or A number of them (for example 2 of 3). Each person counts once: someone who is named and also in a listed group fills only one place. |
| Due date | Optional. Shown to approvers and in the report, where overdue requests are highlighted. |
| Note to approvers | Optional, up to 1,000 characters. |
| Notify approvers | On by default: posts a page comment that @mentions them. |
Up to 25 people and groups per request. Use a group for more people. A page has one request at a time; withdraw it to change the approvers.
Approvers click Approval under the page title, review the page and choose Approve (with an optional comment) or Reject (with a reason, which is required).
Signworthy doesn't send email itself. It posts page comments that @mention people, and Confluence notifies them in the usual way, by in-app notification and email, depending on each person's settings.
| When | Comment | Who is mentioned |
|---|---|---|
| Approval is requested | Posted as the person requesting, with the rule, due date and note | Each named approver, and each member of groups of up to 25 people. Larger groups are named but not mentioned member by member |
| The page becomes approved | "Approved: version N has the approvals it needs" | The person who requested approval |
| The page is rejected | Who rejected it, on which version, and the reason | The person who requested approval |
If a comment can't be posted, for example because comments are turned off for the space, the request or decision is still saved and Signworthy shows a warning.
Open Apps → Signworthy to see every page with an approval request that you can view, with its space, status, approvals, requester, request date and due date. Filter by status and space, or switch on Waiting for me.
Export audit trail (CSV) lists every event, oldest first:
| Column | What it contains |
|---|---|
| time_utc | When it happened, in UTC |
| event | requested, approved, rejected or withdrawn |
| page_id, page_title, space_key | The page, as it is called now |
| page_version | The version the request or decision applied to |
| person, account_id | Who did it: their current Confluence name and Atlassian account ID |
| request_id, rule, approvers, due_date | The request the event belongs to |
| note_or_reason | The request's note, or the approver's comment or reason |
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 withdraw its request from the same dialog. The page goes back to Approval, and the request and its decisions stay in the audit trail.
| What | Where it lives | Who can see it |
|---|---|---|
| Approval requests: page ID and version, approvers, rule, due date, note, and the Atlassian account ID of the person who requested | Your Atlassian site's app storage (Forge storage) | People who can view the page |
| Decisions: approve or reject, page version, time, comment or reason, and the approver's Atlassian account ID | Your Atlassian site's app storage (Forge storage) | People who can view the page |
| Page content | Read as the viewing user to tell whether it has changed since approval (a fingerprint of the content is stored, not the text) | Only people who can already see that page |
| Comments Signworthy posts | On the page, like any other Confluence comment, posted as the person who acted | 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 request approval" | Ask someone with edit access to the page, or a space admin, to request it. |
| "You aren't one of this page's approvers" | Only the people named in the request, or members of its groups, can approve. The requester can withdraw and request again with different approvers. |
| "The page changed while you were reviewing it" | Reload the page, review the new version and decide again. |
| "The comment that notifies the approvers couldn't be posted" | The request is saved. Check that comments are allowed in the space, or tell the approvers directly. |
| Status still shows the old state | The status under the title refreshes when the page loads and when you close the Signworthy dialog. Reload the page. |
| A page is missing from the report | The report only shows pages you can view. Withdrawn requests appear in the audit trail export, not the report. |
| "Signworthy'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 audit trail export still work. |
| Approvals are gone after reinstalling | Atlassian doesn't restore an app's data when it's reinstalled. Keep the audit trail 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 | 6 Nov 2026 | First version: version-bound approvals for pages, status under the title, people and group approvers with all or any-N rules, @mention notifications, approvals report and audit trail CSV. Not yet released. |
Email office@smarteduonline.co.uk with the subject Signworthy support. Please include:
yourcompany.atlassian.netUse of Signworthy is covered by our terms of use and privacy policy.