BlueGrove Labs
Help CenterCompare Any Two PagesConfluence Cloud
Support
中文

Compare Any Two Pages Permissions and Data

Compare Any Two Pages is designed as a read-only comparison tool for Confluence content. It saves recent comparison references and per-user page visit records to help you reopen comparisons and compare a page with the version recorded on your previous visit. Depending on the installed version and administrator settings, it also records site-level comparison usage counts as described below.

Content access

  • Compare Any Two Pages acts for the current Confluence user.
  • Search and comparison results are limited to content that user can access.
  • The app reads the selected document snapshots. When a document references file media, it reads attachment metadata and can download image attachments to display a preview.
  • A permission error or missing page is shown as an error; it is not treated as an empty document.

What Compare Any Two Pages does not do

  • It does not edit, publish, merge, or roll back Confluence content.
  • It does not write comparison marks into either source page.
  • It does not store page bodies, attachments, or complete comparison results in recent history or page visit records.

Recent comparisons

After a successful comparison, Compare Any Two Pages can save up to 10 recent references for the current user. A reference contains the two content IDs, titles, content types, actual numbered versions, and comparison time so the pair can be reopened. These references are stored in Confluence for the current user and site; they are not a team-wide comparison history.

Last-viewed page records

When you open or refresh a published standard Confluence page, Compare Any Two Pages records the page ID, visit time, and current published version so you can quickly compare the version from your previous visit with the current version.

These records are stored in Atlassian Forge app storage, separately for each site, user, and page. They do not contain page bodies, attachments, or complete comparison results, and do not change your Confluence access permissions.

Usage counts

Versions that support usage metrics count comparison attempts, successful comparisons, and failed comparisons through Atlassian Forge custom metrics. We use the counts to understand adoption and use during trials and subscriptions, identify reliability issues, and prioritize product improvements. Ordinary page views do not generate these comparison counts; the last-viewed page records described above are a separate feature.

Each metric sends a fixed name and an increment of one. The app does not attach page bodies, titles, page IDs, user account IDs, or error messages. Atlassian associates the metrics with app, environment, site, version, and module context. Authorized BlueGrove Labs app contributors can view counts by customer site, so these are not completely anonymous statistics or a per-user activity history.

Atlassian processes and stores the counters in its developer metrics service. They are not sent to a BlueGrove Labs-operated analytics backend or a third-party analytics tool. Metrics retention and deletion follow Atlassian platform policies; disabling access or uninstalling the app does not mean historical metrics are immediately deleted. No separate retention period or customer-selected data residency region is promised for these metrics.

Administrators can turn off Custom metrics access for the app in Atlassian Administration: select the relevant site, open Apps → Connected apps, and open the app details. Comparisons continue to work when metrics access is disabled or reporting is unavailable. See Atlassian custom metrics documentation for current controls. Contact [email protected] for privacy questions or deletion requests.

Page changes settings and access

The Page changes macro saves its mode, fixed baseline and optional label, reference and version strategy, and default expansion option as Confluence macro configuration. Each reader still uses their own access to the pages and versions. Selecting a reference as an author does not grant readers access to it.

Since each reader’s last visit uses the personal records described above. Expanding or opening a comparison does not advance the record; reloading the page records a new visit. Visit records and baseline labels are not acknowledgements, approvals, or signatures. Temporary version or direction changes do not update the macro configuration.

See Show changes on a page and Compare with a reference page.

A comparison link contains the content IDs, content types, actual version numbers, and reading mode. It does not contain page bodies or a complete comparison result. Recipients use their own Confluence account and must have access to both pieces of content; a shared link does not grant additional permissions.

Safe fallbacks

Some macros, media, Smart Links, or unsupported ADF nodes cannot reproduce their full Confluence runtime in a read-only app. Compare Any Two Pages keeps them visible through constrained previews or explicit fallback summaries instead of silently dropping them.