Paperlatch

Documentation and support

Confirm & Chase for Confluence

Setting up

1. Edit a Confluence page and add the Confirm & Chase macro where you want the confirmation to appear.
2. Select the macro and open its settings (the pencil in the toolbar above it).
3. Set the text readers will see, and pick the Confluence group that has to confirm.
4. Publish the page.

There are two places to see the results:

• Apps → Policy compliance — every policy across the whole site, with a summary of what is clear and what is outstanding. This is the view for whoever owns compliance.
• The space sidebar, under Space apps — the same report, narrowed to that space, for whoever owns a single space.

Picking a group is optional, but without one the report can only show who did confirm. The list of who has not confirmed is what the group makes possible.

Asking everyone to confirm again

When a policy changes, open the macro settings and choose Save & require everyone to confirm again.

This raises the policy version. Everyone is asked to confirm the new version, and the previous round stays on record exactly as it was given. Both rounds appear in the CSV export, so you can still show who accepted version 1 after version 2 has gone out.

The report

Opening a page in the report shows two tabs:

• Not confirmed — people in the audience who have not confirmed the current version, and whether they confirmed an earlier one
• Confirmed — who confirmed, and when

Download CSV produces the full history: every person, every version, every timestamp, including rounds that are no longer current. It is written with a byte order mark so that Excel opens it as UTF-8.

Common questions

Someone says they clicked, but the report shows them as not confirmed.

Almost always this means they confirmed an earlier policy version. The report says so in the Note column. If the policy version was raised, every reader has to confirm again.

My group shows as empty, or the count looks wrong.

Confluence has several groups whose names look similar. Groups such as confluence-user-access-admins-… control permissions and are often empty. Pick the group that actually contains the people who have to read the page.

Why is the number smaller than the group size?

Service accounts belonging to installed apps are members of some Confluence groups. They cannot click a button, so the app leaves them out of the count. The report counts people.

Can I assign the page to individual people instead of a group?

Not today. The audience is a Confluence group. If you need a specific set of people, create a group containing them.

Can I set a deadline, or send reminder emails?

No. The app shows you who is outstanding; chasing them is done however your organisation already does it. If deadlines and automated reminders are a requirement, this is not the right app for you, and it is better to know that before you install it.

I edited the page. Does everyone have to confirm again?

No — not unless you say so. Editing a page does not reset confirmations, because most edits are typos rather than policy changes. When a change is material, use Save & require everyone to confirm again.

Does it work in the Confluence mobile app?

The confirmation button and the report are built for the browser. Confluence's mobile apps do not render this kind of macro reliably. Use a desktop browser.

What happens to the confirmations if I uninstall?

They are stored in Atlassian's app storage inside your site, and Atlassian deletes that storage when the app is removed. Export the CSV first if you need to keep the record.

Support

Email support@paperlatch.com on business days. We aim to reply within two business days.

To get a useful answer in the first reply, include:

• your Confluence site URL
• the page where the problem appears
• the name of the group you selected as the audience
• what you expected to see and what you saw instead
• a screenshot of the report, if the question is about a number

Security and privacy

The app runs on Atlassian Forge. Its data stays in Atlassian's app storage inside your site, and we operate no server. It requests read-only permissions and never asks to write to your content, to act on a user's behalf, or to read email addresses. You can verify this yourself on the Permissions tab of the Marketplace listing.

See the Privacy Policy for exactly what is stored.