App Documentation / User Guide

Overview

Confluence content goes stale silently. Onboarding guides, runbooks, and process docs can sit for years without review, and readers have no way to tell what's current. Page Pulse makes freshness visible at the point of reading and turns cleanup into a workflow your space admins will actually use.

It runs entirely on Atlassian's Forge platform — there is no external server and no data egress.

Getting started

• Install Page Pulse on your Confluence site (from the Atlassian Marketplace, or via an installation link from your administrator).
• Open any space you administer. In the space's left sidebar, find Page Pulse.
• The first time, you'll see "No scan results yet." Click Run first scan. The scan runs in the background and also runs automatically once a day.
• After the scan completes (typically a few minutes), open any page in the space — a freshness indicator appears in the byline under the page title. Click it for details and actions.
• Adjust policy under Space settings → Page Pulse (threshold and excluded labels).

Features

Freshness byline

Every page shows its status in the byline — with the last meaningful update date:

The indicator is cached, so it adds no load to page views. Click it to open a detail popup with the full breakdown and the review actions.

Daily scan

Once a day, Page Pulse scans every global space, scores each page, and updates its freshness indicator. The scan is built to handle very large spaces (up to tens of thousands of pages) reliably by processing them in batches.

Stale-page report (space admins)

The Page Pulse report in the space sidebar lists pages ranked by staleness, with the page age and owner. It flags pages whose owner may no longer be active, lets you filter by label, and offers a one-click Request review on each row.

Review workflow

• Request review — flags the page and notifies its owner. Duplicate requests are coalesced into one.
• Mark as reviewed — available to the page owner or a space admin. It resets the freshness clock without needing a cosmetic edit, and records who reviewed it and when.

Per-space settings

• Staleness threshold — 6, 12, or 18 months, to match how fast that space's content changes.
• Excluded labels — pages carrying labels such as archive or evergreen are skipped and show no freshness indicator.

Saving settings queues an immediate rescan of that space, so changes take effect within minutes.

How freshness is calculated

For each page, Page Pulse takes the last meaningful update — the later of the page's last edit date and its last manual "Mark as reviewed" date — and compares its age against the space's threshold (T):

The report ranks pages by a staleness score derived from that age, with extra weight when a page has no owner or its owner may be inactive — so the pages that most need attention rise to the top.

Known limitations

• "Owner may be inactive" is a best-effort signal, not a fact. Atlassian does not expose account-deactivation status to apps, so Page Pulse infers it (for example, when an owner lookup returns no active profile). Treat it as a prompt to check, not a definitive statement.
• The scan covers global spaces and current (non-archived) pages.
• The report displays the top 200 pages by staleness; the full page and stale counts are shown above the table.

Data & privacy

Page Pulse stores only Confluence page metadata (titles, dates, labels, and page-owner identifiers) inside Atlassian-hosted Forge storage. It does not read or store page body content, sends nothing to any third party, and collects no credentials. Full details are in the Privacy & Data Handling statement.

Support

Questions, issues, or feedback? Email info@buzzclan.com and we'll help.