Review Due — documentation
Review Due adds a review date, an owner and a review cadence to any Confluence page, brings your tracked pages together on one dashboard (up to 5,000 in a single load, as described below), and reminds the owner on the page itself when the date is near or past. This page describes how to install it and how to use it. It says what the app does today; if something here does not match what you see, write to support@northwick-apps.com.
1. Install
Availability: Review Due is on the Atlassian Marketplace since 16 October 2026 — marketplace.atlassian.com/apps/1448228180/review-due.
A Confluence site admin installs the app from its Atlassian Marketplace listing with Get it now, or from Settings > Apps > Find new apps inside Confluence. There is nothing to configure after installation: no admin screen, no field to add to a template. Sites with up to 10 users use the app free; larger sites are billed by Atlassian per user per month (see the FAQ for the tiers).
Where it appears. The app's two screens — Review status under the page title and the Apps > Review Due dashboard — are Forge app surfaces, and Confluence loads those in its desktop web interface only. The Confluence mobile app and a phone browser's mobile layout do not show them; a phone browser set to Desktop site does, and everything works there. The reminder is different: it is an ordinary comment on the page and not an app surface, so it reaches a phone like any other comment, and a reviewer told on a phone that a page is due marks it reviewed from a computer — the record is the same either way. Nothing in the app changes this.
If “Review status” is not under the page title. Since 28 October 2026 Confluence shows a single row of app items under a page title by default and hides the rest behind the row, so on a site with several apps ours can start out hidden. Expand the byline and Review status is there; a Confluence administrator can switch the default back for everyone under Confluence administration > General configuration > "Show all byline apps by default". Nothing in the app changes either way.
2. Set a review date on a page
- Open a published page. A draft has no permanent page ID, so the app shows "Publish the page first" until the page is published.
- Under the title, in the byline, click Review status.
- The first time, Confluence asks you to let the app act as you: click Allow access. The app uses this to ask Confluence, before every read or change, whether you may see and edit that specific page. Page restrictions and space permissions decide; there is nothing to configure in the app.
- Pick the page owner (the person who will be reminded), the next review date, and a cadence: every 30, 90 or 180 days, or every year.
- Click Start tracking.
The byline then shows the state on the page, for example Review due 2026-08-12 · every 180 days · last reviewed 2026-02-12, coloured green (OK), yellow (due within 14 days) or red (overdue). Anyone who can edit the page can set or change its review date; anyone who can view it can see the status.
3. Mark a page as reviewed
When the owner has checked that the page is still correct, they click Mark as reviewed in the byline. The app records today as the last review date and moves the next review date forward by the page's cadence. Editing the page does not count as a review: Confluence already records edits, and Review Due deliberately tracks the check, not the edit.
4. The dashboard
Open Apps > Review Due in the Confluence top bar. The dashboard lists the tracked pages you are allowed to read, with each page's space, review date, status (Overdue, Due soon, OK) and last review date, sorted by review date; each title links to the page. A counts line above the table reads, for example, 6 tracked · 2 overdue · 1 due soon · 3 fresh. Two toggles narrow the list: Show only pages that need attention (on by default) and Only my pages.
The list is filtered per person: the app checks your permission on each page before showing the row, so two people on the same site can see different rows. When the dashboard finds that a tracked page has been deleted or moved to the trash, it removes that page's record at once.
How many rows one load shows. The dashboard reads tracked pages in batches of 100 and stops after 50 batches, so one load shows at most 5,000 of them. A site with more than that sees a line above the table saying how many it is showing, for example “Showing the first 5,000 tracked pages.” — nothing is lost, and the pages that are not on screen keep their review dates and their reminders; only this one list is cut. We say so here, and in the two sentences above that used to read “every tracked page” until 28 October 2026, because on a very large site that phrase was not the whole truth.
5. Reminders
Once a day the app works through the tracked pages on the site. A run is time-boxed — Atlassian allows it about a quarter of an hour, and part of that is kept for housekeeping — and it remembers where it stopped, so a site with more pages than one run can reach continues the next day from that point rather than starting over. No page is skipped, but on a very large site a reminder can arrive a day later than the review date. When a page is overdue, or due within the next 14 days, and has an owner, the app posts a comment on the page that @-mentions the owner, who is then notified by Confluence in the usual way. A page is reminded at most once a week, so a forgotten document does not become a stream of comments. The app never sends email of its own. Atlassian schedules the daily job, so the exact hour is not promised.
6. Stop tracking a page
Click Stop tracking in the page's byline. The page's record is deleted immediately; nothing on the page itself changes. Earlier reminder comments stay on the page like any other comment and can be deleted by whoever may delete comments there.
7. Permissions, in one paragraph
Before the app shows or changes anything about a page, it asks Confluence whether you may view or edit that page, and it fails closed: if the check cannot be completed, the action is refused. The daily reminder job runs as the app, within the permissions the app declares, and never as a person. The scopes the app asks for are listed on the Marketplace listing and justified one by one on the Security page.
8. Your data
For each tracked page the app stores the page ID and title, the space key and name, the page link path, the Atlassian account ID of the owner, the cadence, the review dates and status, and the bookkeeping for the reminder it posted. It stores no page content, no comments, no names and no email addresses. Everything lives in Atlassian's Forge storage in your site's region; nothing leaves Atlassian. Stop tracking deletes a page's record immediately; uninstalling the app makes Atlassian soft-delete the app's storage and delete it permanently after 28 days. The Privacy Policy lists every field.
9. Subscription and billing
Billing is by Atlassian, through your site's subscription. If the subscription lapses, nothing you recorded disappears: review dates, owners and the dashboard stay readable. Changing a review date and the reminder comments pause until the subscription is active again. “Stop tracking” keeps working, so a site whose subscription has lapsed can still delete a page's record at any time — the privacy policy promises that deletion with no conditions attached, and from version 2.0.3 the app keeps that promise.
10. Getting help
The FAQ answers the questions that come up in practice. For anything else, see the Support page: email support@northwick-apps.com and you get an answer within one business day (Sunday to Thursday, Israel time).