Northwick

Acknowledge — questions and answers

Updated: 28 October 2026 · Applies to Confluence Cloud

Acknowledge asks a group of people to confirm they have read a page — a policy, a handbook, an SOP — and keeps the record of who confirmed which version, and when. It is a Confluence Cloud app from Northwick and is being prepared for the Atlassian Marketplace. The answers below describe what the app does today, written from its code. Answers about our other app are on the Review Due FAQ; if your question is not on either page, write to support@northwick-apps.com and the Support page says what to include and how quickly we reply.

Setting up a requirement

Who can set a requirement on a page, and who can see the report?

Anyone who can edit the page can set the requirement, change it, or stop tracking. The full report — every person in the group with their status, the version they acknowledged and when — is visible to people who can edit that page and to administrators of the space the page is in now, provided they can also see the page; those are the people who can export it. Both halves are asked of Confluence at the moment of the call, so a page restriction that excludes an administrator closes the report to them, and after a page is moved it is the new space's administrators who can open it. Someone who is only in the group sees their own status on the page and nothing about anyone else. The dashboard under Apps → Acknowledge lists only pages you are allowed to read, so two people on the same site can see different rows.

The byline says "Publish the page first"

Acknowledge works on published pages. While a page is a draft, Confluence has not given it a permanent ID yet, so there is nothing for an acknowledgement to be recorded against. Publish the page and the byline will let you set the requirement.

Someone edited the page — does everyone have to acknowledge again?

That is your choice per page, in the requirement's settings. Latest version — the default, and the right setting for a policy — means a new version of the page puts everyone back to Please acknowledge, and the report shows which version each person signed. Pinned version means people must have acknowledged that version or later, so ordinary edits like a typo or a broken link reset nothing. You can move the pin later from the report. Whichever you choose, the report and the export always name both the version each person acknowledged and the version currently required.

Our group has more than 5,000 people

Acknowledge records an audience of up to 5,000 members per group and will not set a requirement on a group larger than that. The way forward today is a smaller group — often the right one anyway, since an acknowledgement asked of everyone tends to be acknowledged by no one. If the limit is in your way, tell us: we write every such request down, and we will not promise a change or a date for one.

Does it work on blog posts, on several pages at once, or on Data Center?

Acknowledge is a Confluence Cloud app built on Atlassian Forge, and there is no Data Center or Server version. A requirement is set one page at a time, from that page's byline. For anything else in that list, tell us what you are trying to do and we will answer from the app rather than guess — if it is not supported, we say so plainly.

Does it work on a phone?

The screens do not, and that is not something we can change in the app. Acknowledge's three surfaces — the app's item under the page title (Please acknowledge when you still have to confirm, Acknowledge before anyone has set a requirement), the acknowledgement report in the ••• menu, and the Apps > Acknowledge dashboard — are Forge app surfaces, and Confluence loads those in its desktop web interface only: in the Confluence mobile app, and in a phone browser's mobile layout, they are not shown at all. A phone browser switched to Desktop site does show them, and they work there. The weekly reminder is different: it is an ordinary page comment with an @mention and not an app surface, so a phone shows it the way it shows any other comment on the page — a reader can see on a phone that they are being asked, and confirm from a computer. Nothing is lost by waiting: an acknowledgement made on a laptop records the same person, the same page version and the time. Atlassian publishes no support matrix for app surfaces on mobile, so this is what we observe on our own site rather than a documented rule.

The Acknowledge item has disappeared from under the page title

Nothing has been uninstalled. Since 28 October 2026 Confluence shows one row of app items under a page title by default and hides the rest behind the row; which apps are in that first row depends on their order, how many apps the site has installed and how wide the window is. Expand the byline and the item — with I have read this on it — is there, and every acknowledgement already recorded is untouched. If you would rather everyone saw every app item straight away, a Confluence administrator can turn that on for the whole site under Confluence administration > General configuration > "Show all byline apps by default".

Acknowledging a page

Somebody asked me to acknowledge a page — what do I click?

Open the page in Confluence and look under its title: there is an item that reads Please acknowledge. Open it and click I have read this (version N). The item then reads Acknowledged and keeps the version you confirmed and the time, which is the whole record — there is nothing else to fill in and nothing to send. If it reads Not required, you are not in the group that page asks, and nothing is expected of you.

Two things catch people out. The item is one of the app's screens, so it needs Confluence in a desktop view: on a phone you can see the weekly reminder comment but not the item itself, until you switch the browser to Desktop site (in Safari, Request Desktop Website) or open the page on a computer — an acknowledgement made later, on a laptop, records exactly the same thing. And if the page is edited after you confirm, a requirement set to re-request on every new version puts the item back to Please acknowledge: that is the setting doing its job, not a lost record. Your earlier confirmation stays in the report against the version it was made on.

It keeps asking for permission, or I clicked and nothing happened

Acknowledge asks Confluence, as you, whether you may read or edit each page before it shows or changes anything — that is the "Allow access" prompt. Click Allow access, then Try again. If the prompt comes back a second time, send us your site URL and the app version from Manage apps: a prompt that repeats after consent means the app is asking for something it has not declared, which is our bug and not your configuration.

I clicked "I have read this" and it says I am not in the group

When you click, the app re-checks with Confluence whether you are in the group that page asks to acknowledge, and records nothing if you are not. Two things cause the message: you are genuinely outside that group, in which case nothing is expected of you and the page will say Not required; or you were added to the group very recently and the app is still holding the membership list it read a few minutes ago, which it refreshes within about fifteen minutes. If it is still wrong after that, send us the page and the group name.

"Acknowledge could not check the group membership right now"

That means the app asked Confluence who is in the group and did not get a usable answer, so it deliberately recorded nothing rather than record an acknowledgement it could not verify. Try again in a minute. If it keeps happening, send us the page and the time and we will read the app's log — for a compliance record, missing is better than possibly wrong, which is why it fails this way.

Reminders

Who gets reminded, when, and how often?

The reminder is a comment at the bottom of the page itself, and it @-mentions people in the group who have not yet acknowledged the current version. It starts no earlier than seven days after the requirement is set, and the same page is never reminded more than once every seven days. One comment mentions at most 25 people; when more are outstanding it says how many more, and the next reminder mentions the next 25, so everyone is reached in turn. After the due date the comment also mentions whoever set the requirement up, so the page owner knows it is overdue. You can turn reminders off for a page in its settings, and you can delete our comments at any time — it changes nothing about who has acknowledged.

Does it send email?

No. Acknowledge never sends email. It writes a comment and mentions people; every notification you receive about it comes from Confluence, under your own notification settings.

What time of day does it run?

Once a day. Atlassian schedules the exact time for a daily app job and that time moves, so we do not promise an hour. What the app guarantees is one pass per day per site, and that the same page is not reminded twice for the same round even if a pass is interrupted.

The report and the export

Can we get this out for an auditor?

Yes. The report exports as a CSV with one row per person in the group: the page, the space, the group, the person, their status, which version they acknowledged and when, the current and required versions, the due date and the time of the export. By default it identifies people by their Atlassian account ID. Tick Include names before exporting and the app resolves display names — that option exists so an export can be pseudonymous when your privacy rules ask for that, and named when an auditor asks for that.

We removed someone's acknowledgement and they are still in the report

That is deliberate. Remove acknowledgement does not erase anything: it marks the acknowledgement as removed, with the time and who removed it, and puts that person back to Please acknowledge. The History tab still shows that they had acknowledged, which version, and who removed it and when; the report and the export show that it was removed and when — because an acknowledgement record that can be silently deleted is worth nothing to an auditor. If you want one person's data erased rather than marked, use Erase this person's data on this page, under More ⋯ on the same row — the answer below says what it does. If you want a page's data gone entirely, use Stop tracking: that erases the requirement and everyone's acknowledgements for that page.

Somebody asked us to erase their acknowledgement, not just remove it

In the report, turn off Only people who have not acknowledged if the person has acknowledged, click More ⋯ on their row, then Erase this person's data on this page. It arms for ten seconds as Confirm erasure and then deletes that person's acknowledgements and history on this page for good; other pages are not affected. They count as pending from that moment, so a page that still has a requirement may ask them again and the next reminder may mention them — remove the requirement first, or take them out of the group, if that is not what you want. What stays is one line in the History tab, erased a person's data, saying who did it and when, with nothing about whose data it was; the page keeps the newest 50 of those lines. Anyone who can edit the page, and an administrator of its current space who can see the page, can do it. We cannot do it for you: nobody at Northwick can read or change what the app stores in your site.

A page we deleted is still on the dashboard

A tracked page that has been deleted stops showing its title, group and creator and appears as Page <id> (deleted) with its counts, so the requirement can be cleaned up. Administrators of its space can click Stop tracking and then Confirm: stop tracking on that row straight away; that stops tracking the page and erases its acknowledgements and history, and a later restore does not bring them back. After 30 days anyone who can see the dashboard can. If a row survives that, send us the site URL and the row.

Data, pricing and subscriptions

What do you store about us, and how do we get it deleted?

For each page with a requirement we store one record: the page ID and title, the space ID, key and name, the link path Confluence reports for the page, the ID and name of the group that must acknowledge, the version mode and the versions involved, the optional due date, whether reminders are on, the account ID of the person who set it up, timestamps, the reminder bookkeeping, cached counts, a timestamp if the page is found deleted, the time and account ID of whoever deleted an acknowledgement record (the newest 50, and nothing about whose record it was), and a mark while a Stop tracking is still working through the page. For each person who acknowledges we store the page ID, their account ID, the space ID, the highest version they acknowledged and when, a capped per-version history, and — if a page editor removed it — when and who removed it. No page content, no comments, no attachments, no email addresses. Everything stays inside Atlassian's Forge storage in your site's region; we run no servers and no database of our own. The Privacy Policy lists it field by field and the Security page explains how it is protected.

To delete everything for one page, click Stop tracking: the requirement and all its records go. On a page with thousands of records it works to a fifteen-second budget — reminders go off before the first record is deleted, and if it runs out of time it tells you how many it deleted and asks you to click again to carry on, so a page in that state asks nobody to acknowledge it in the meantime. To erase one person's data on a page, use Erase this person's data on this page, under More ⋯ on their row in the report. To delete everything, uninstall the app — Atlassian then holds the app's storage for 28 days before deleting it permanently, and a site admin can ask Atlassian within 21 days to re-link it to a reinstalled copy. We cannot read or recover that retained data ourselves.

How much is it?

Free for up to 10 users on your site, then $0.95 per user per month from 11 to 100 users, with lower per-user prices in the larger tiers. Atlassian bills it, not us, and the Marketplace listing shows your exact price for your user count — that listing, not this page, is the authority.

What happens if our subscription lapses?

Nothing you have already collected disappears or becomes unreadable. The report, the dashboard and the export keep working, people can still acknowledge pages, and you can still stop tracking a page or remove a record. What pauses is setting up a new requirement, changing an existing one, and the reminder comments, until a site admin renews under Confluence → Apps. A record you have already collected is your data, so the app never holds it behind a subscription.

Still stuck

Write to support@northwick-apps.com. We reply within one business day (Sunday to Thursday, Israel time), and we answer from the code: if the app cannot do something, we say so plainly rather than promising it.