Documentation

Page Acknowledgements user guide

How to use the app and understand its limits.

Product overview · Support

Ask people to acknowledge a Confluence Cloud page version, then review their responses. Readers confirm for themselves. Only editors manage and see reports: every management or report action checks your current permission to edit the page. The request creator can also delete their own request from Requests I manage, including when the page is no longer available. Confluence admins have separate privacy and cleanup settings.

Installation and access

Marketplace publication is pending. Once the app is listed, a Confluence admin can install it from Atlassian Marketplace for the site and review its permissions. The app uses Confluence pages, page markers, groups, user details, access checks and Atlassian-hosted storage. It does not change page text or send email.

Use Confluence Cloud in a web browser with a licensed Atlassian account. Open Acknowledgements from the page actions to manage a request or view its report. Open Page Acknowledgements from Confluence Apps for your personal lists. If Confluence asks you to Allow access, grant access and try the action again. An inactive app license hides the banner and blocks ordinary app use; authorized privacy lookup, deletion and marker removal remain available.

Request acknowledgements

  1. Open the current published page. You must be able to edit it.
  2. Open Acknowledgements. An empty page shows No acknowledgement requested for this page yet.
  3. Enter a group search in Find groups, choose Search groups, then select Groups. More groups continues the search. You can also select People.
  4. Optionally choose Due date (optional, end of day UTC). The deadline is the end of that date in UTC and must be in the future.
  5. Choose Request acknowledgements. A request can include up to 20 groups and at most 2,000 people, after combining groups and individual selections.

The app saves the request and then adds a page marker to enable its banner. This does not edit the page body. If it shows Readers won't see the banner yet—try again, use Try again to restore the marker. Do not assume readers can see a banner until that step succeeds.

Read and confirm

Recipients see a banner on pages with an active request. Read the current page, then choose Confirm. The app checks that you can still open the page and records the current version and the first confirmation time. Repeated clicks do not create duplicate confirmations for the same person and version.

If the page changed after the banner loaded, the message is This page was updated to version <version>. Reload the page to review it before confirming. The version number identifies the current page. Choose Reload page, read the current version and confirm again. An old page-history view shows You're viewing an older version. Open the current page to confirm. A lost permission shows You can't open this page anymore, so it can't be confirmed.

A later edit does not itself require everyone to confirm again. Existing confirmations continue to satisfy the requested version until an editor chooses Request again. The banner can briefly show an older version until a confirmation, management action or weekly check observes the change; confirmation always checks the current page before saving.

My acknowledgements

Open Page Acknowledgements in Confluence Apps, then My acknowledgements. This lists your open requests, requested versions and due dates. Overdue. marks a request past its deadline. Open its page link to read and confirm. Load more continues the list; a list section can be empty while more remain. When there are no remaining requests, it shows You're all caught up. Nothing to acknowledge.

Confirmed and closed requests are omitted. Pages you cannot open contribute only to a hidden count, without a title or link: 1 request is on a page you can't open right now. If you can open a page that the app cannot see, its row can still show Page unavailable to the app; your own access is checked separately.

Requests I manage

Choose Requests I manage in the same app view. This lists requests you created, their state (active, closed, or deletion in progress), versions, changes since the request and the number of confirmations removed for privacy. Use Load more to continue. This list is not a report about other recipients; opening the page's management view or report still requires current editing permission.

If you cannot open a page, the row shows Page unavailable without its title. When the weekly check found it unavailable to the app, a separate notice says Page unavailable to the app. A restriction and a deleted page cannot be told apart reliably. The explanation is The app can't see this page—it may be deleted or restricted. Records are kept until you delete them. The creator can choose Delete records from this list after reviewing the warning.

Report, CSV and summary

On the page, open Acknowledgements, then View report. Only people who can open the page count as open. If another person's access cannot be verified, the app shows Access not checked, with The app can't check this person's access. It does not assume access from a failed check.

StatusMeaning
ConfirmedThe person confirmed at least the requested version.
Confirmed an older versionThe person has a confirmation below the requested version and can open the page.
OpenNo qualifying confirmation; access to the page was checked successfully.
Cannot view the pageThe access check says this person cannot open the page.
Access not checkedAccess could not be established; this is separate from Open.

Only Open and Confirmed an older version can be overdue. Cannot view the page and Access not checked are never counted as overdue in the report, summary or CSV.

Next report page continues the report. Counts cover people checked so far; continue until there is no next page for complete counts. The report also counts previous participants outside the current request and confirmations erased for privacy. Refresh report starts a fresh report. Changes to the request or an expired continuation can require opening it again.

Choose Show CSV to copy for the displayed people, or Show summary to copy for the current counts. Select the text in CSV for the displayed people or Summary to copy and copy it yourself. CSV includes only the displayed people, not every report page. Its Due date (UTC) column holds the request's due date as YYYY-MM-DD, and stays empty when the request has none. Names and the page title are fetched for display/export and exist only in the browser or the current response, never in saved records. CSV text is protected against spreadsheet formulas. There is no file-download button and no automatic message sending. Your organization controls any copy you save or send.

Refresh, request again and close

New group members appear after Refresh. An editor must choose Refresh group members; group membership is not synchronized by the weekly check. Refresh is available at most once every 10 minutes. It adds current group members, removes people no longer in the selected groups and retains individually selected people. People whose data is being deleted are skipped, and the message says how many. Earlier confirmations remain as history when somebody leaves the audience.

Choose Request again to set the requested version to the latest observed page version and start another request round. Earlier confirmations remain; people who already confirmed the new requested version do not need to repeat it. Close request ends the active request and removes its marker. It shows This request is closed. Records are kept. If marker removal fails, use Try again. Closing is different from deleting the records.

Monthly usage allowance

Every site has a monthly usage allowance for the app, counted in UTC months. It grows with the number of people who use the app on the site. When it runs low, the app turns work away in a fixed order: first the weekly page check, then creating and updating requests, refreshing members and reports, then the lists and the request settings, then banners that ask you for nothing, and last confirmations and banners that ask you to confirm. The last quarter of what banners and confirmations share is kept for people who still have something to confirm: when the plain banner views have used up their part, a banner still shows the request and the Confirm button to anyone who has to confirm. A banner or a confirmation that is turned away at that point still reads a little, and that is counted against the same last quarter: if very many people who have nothing to confirm open pages that carry an acknowledgement request, the confirmations of that month can pause earlier. While very many people open such pages at the same moment and little of the allowance is left, a banner can say Couldn't check your acknowledgement status just now. Reload the page to try again. instead, with a Reload page button; use it to check again a moment later. Once what is left cannot carry another confirmation, the banner shows the notice below, and the app spends next to nothing on further views until the new month starts. A paused action says what is paused and until when, for example Confirmations are paused until <date> (UTC). This site has used its monthly usage allowance for the app. Nothing is lost: saved requests and confirmations stay as they are, and the paused action works again when the new month starts. The banner then shows this notice instead of the Confirm button. The weekly report of stored account IDs to Atlassian and the erasure of closed accounts do not depend on what the other actions have used: they run every week, also when everything else has been paused. Deleting records keeps working up to a limit of its own, whatever the other actions have used. A very large stock of records can need more than one month to delete; the deletion then says until when it is paused. A list of people you typed in that is larger than a small site's allowance allows is not accepted; the app says how many people fit, and the members of a chosen group count toward the allowance. If the app cannot check its allowance for a moment, it asks you to reload the page or try again.

Delete records and remove markers

Page acknowledgement records are never deleted automatically because a page is deleted, moved to trash or restricted. Those records remain until explicit deletion. Account closure and uninstall retention are separate deletion paths described below. A weekly check only marks unavailable pages; it does not delete their acknowledgement history.

An editor can open Delete acknowledgement records from the page actions. A request creator can use Delete records in Requests I manage. Choose Confirm deletion only if you want to remove the page's request, recipient records and acknowledgements. This cannot be undone. A partial operation shows Some records remain. Continue the deletion to finish. Use Continue deletion until completion. The app's storage can list a new record a little late, so the deletion always ends with a final check. Until then the panel shows All records we could find are deleted. A final check finishes the deletion automatically, usually within a week; large sites can take longer. You can also continue the deletion yourself in <minutes> minutes. The minutes are the time left. Continue deletion stays closed during the wait, because an earlier click could not finish the deletion. While the check is pending, the request is hidden, nobody can acknowledge it and nobody can create a new request for the page. It stays in Requests I manage as Deletion in progress, with Continue deletion, and Confluence admins find it under Find unavailable pages. A page you cannot edit can retain its marker even after its records are deleted; the marker contains no personal data.

Before uninstalling, a Confluence admin can open Page Acknowledgements in Confluence settings, choose Remove page markers and Confirm. Records are kept. Use Continue for remaining batches and review the number of pages that could not be changed. Pages the admin cannot edit and copied pages without a saved request can retain markers. Markers alone do not contain account IDs, names or acknowledgements.

Admin cleanup and a person's privacy request

The Confluence settings view is titled Acknowledgement records and checks Confluence administrator permission on the server. Choose Find unavailable pages to review requests unavailable to the app for at least 30 days. A restricted page can appear here too, and so does every request whose deletion is waiting for its final check, whatever its age. Delete page records, followed by Confirm, removes the selected page's records; for a request that is being deleted the button reads Continue deletion and opens when the wait is over. Use Continue if needed; the list itself never deletes anything.

For a person's access request, select Person, then Find person's records. The view returns recipient-record, acknowledgement, creator-reference and recovery-record counts per request, plus account records for privacy reporting. Use Load more records until All results loaded. Counts can be incomplete before that. This is a record inventory, not a download of page contents or a full confirmation-history export.

For erasure, choose Delete person's records, review the warning and choose Confirm. It erases their recipient records, acknowledgements and creator references across every page, including results not yet loaded, and removes their references from temporary recovery records. Other people's confirmations remain. Use Continue until completion. The app's storage can list a new record a little late, so each erasure, including Delete page records, ends with a final check: the view then says All records we could find are deleted. A final check finishes the deletion automatically, usually within a week; large sites can take longer. You can also continue the deletion yourself in <minutes> minutes. Continue stays closed during the wait. While the check is pending, the person's account record stays and the person is left out of requests. When you save a request or refresh the members, the message says 1 person was skipped because their data is being deleted. (or the matching number of people), and nothing about that person is saved. After the deletion has finished, a person who is still in a selected group is an ordinary recipient again at the next refresh. A weekly privacy report to Atlassian also processes an account-closure response of closed through this erasure path, and the same weekly run performs the final checks. Weekly work is bounded; a large backlog can need more than one run.

Data, residency and uninstall

No names, titles or content stored: persistent records contain only recipient, confirming-reader and creator account IDs; page, space and group IDs; version and round numbers; times; counts and technical recovery/coordination information. Account IDs are personal data. Names, email addresses, avatars, page titles, group names and page bodies are not stored in records or app logs.

Data stays in Atlassian. Processing and persistent storage use Atlassian Forge, with Atlassian as the sole direct app subprocessor. Hosted storage follows the Confluence location under Atlassian's data residency lifecycle. No independent residency certification or Switzerland-only hosting is claimed. No external app backend or AI receives this data. Customer-created exports and voluntary support messages are separate copies under their respective retention rules.

Uninstall through Confluence's app management. Forge retains hosted data for 28 days after uninstall. Reinstalling does not restore it automatically. With customer consent, a recovery/relink request must be raised within 21 days; this request window is separate from retention and recovery is not guaranteed. Remove markers and make any needed report copies before uninstalling. License expiry or subscription cancellation alone does not erase records.

Limits

  • Pages only (no blog posts). Both page actions show Acknowledgements work on Confluence pages. Blog posts aren't supported. on a blog post.
  • No automatic reminders. Use the banner, personal list and summary you copy; the app sends no emails, notifications or mention comments.
  • This is not a signature, approval workflow or proof that someone understood the page. A confirmation records their action for a page version.
  • No guests or anonymous users.
  • No Live Docs. Live docs aren't supported yet. Publish the page first.
  • The banner is not available in native mobile apps. Use a web browser.
  • On a phone, Atlassian's own Open in app bar can cover the banner in the web browser, and the app cannot move or hide that bar. Find your open acknowledgements under My acknowledgements (Confluence Apps, then Page Acknowledgements) instead.
  • At most 2,000 recipients per page and 20 selected groups.
  • New group members require Refresh group members by an editor; no weekly audience synchronization.
  • Access checks can be unavailable. Access not checked never counts as Open.
  • Confirmations, requests, reports and weekly checks have usage and time limits. A busy Confluence response says Confluence is busy. Try again in <seconds> seconds. A monthly pause says what is paused and until when, for example Confirmations are paused until <date> (UTC). This site has used its monthly usage allowance for the app. See Monthly usage allowance for the order in which work pauses. If usage cannot be checked, a banner shows Couldn't check your acknowledgement status just now. Reload the page to try again. with Reload page; other actions show Usage could not be checked just now. Try again in a moment. There is no promise of unlimited usage or automatic background reminders.
  • A temporary service pause shows Acknowledgements are temporarily paused. Please try again later. in the banner or New work is temporarily paused. Please try again later. in other actions.