Frequently asked questions

StagBane is a Confluence Cloud app that ranks every page in the spaces you choose into an explainable review queue- Critical, Stale, Watch, or Healthy- and names the exact rule that placed each page there. It gives Confluence site admins a systematic, prioritized way to find pages that have quietly gone out of date: unowned, unreviewed, orphaned, or pointing at pages that no longer exist.

It also includes the Page Health Auditor, a Rovo agent that reads individual pages on demand and gives a grounded second opinion on whether the content still holds up- the kind of staleness no timestamp can catch.

Confluence makes it easy to write a page and hard to notice when it stops being true. An onboarding guide describes a tool you retired last year. Two policy pages give contradictory answers. A runbook links to pages that were deleted. The page still loads, still appears in search, and still reads as authoritative.

That was a manageable risk when human readers brought their own skepticism. It is a larger risk now that Rovo and Confluence search surface those same pages as answers. StagBane makes that decay visible and reviewable- without guessing, and without ever changing your content on its own.

The review queue is for Confluence site admins and knowledge managers- it is admin-gated, so only site admins can open it. The Rovo agent (Page Health Auditor) is available to any licensed Rovo user in Rovo chat. Every licensed user benefits indirectly: a reviewed corpus reduces the risk of Rovo surfacing outdated pages as answers.

Yes, in two ways. First, the review queue includes an Audit action on every row that opens the Page Health Auditor pre-aimed at that page- a one-click way to ask whether a page's content still holds up. Second, the Page Health Auditor is available directly in Rovo chat for any licensed Rovo user, independently of the queue.

Rovo is optional for the review queue. The queue's banding, signals, and all other actions work without Rovo enabled.

A small trust badge in the page byline- the one surface every reader sees. It is positive-only: readers see a green "Verified <date>" badge only when a human vouched for the page within the review window. Any other monitored page shows a neutral "Page health" marker instead. Readers never see bands. A site admin who opens the badge popover sees the full band, its reasons, and a link into the queue- the same detail admins already have in the review queue.

No. StagBane never archives, deletes, moves, or rewrites a page. The only things it can add to your content are its own labels (verified-current, needs-review, pha-evergreen), a review date, and a single footer comment when you use the Request Owner Review action. Every other operation is read-only. Humans decide and act.

No- only internal links, meaning links between pages within your audited Confluence spaces. External URLs are never examined, and neither are links into spaces you didn't choose to audit. This is stated up front because it is the expectation most likely to differ from what buyers assume. If you need external link checking, StagBane does not cover that in v1.

No. StagBane surfaces and ranks pages for human review. It never automatically updates page content, review dates, or any other attribute. Every change to your content is one a human triggered.

No. The scanner runs once daily and is incremental- on each run, it re-reads only pages whose version changed since the last scan. The Rovo agent is on-demand and per-page: it audits specific pages you ask about in Rovo chat. Neither surface monitors pages continuously.

No. The Page Health Auditor reads specific pages you ask about in a Rovo chat conversation- only the scheduled scanner scans, and only the spaces you chose to audit. If you are a site admin, you can also ask the agent for the queue's ranked stale list or a space's Rovo-readiness view right in chat- that is a read of the existing index, not a scan, and non-admins are refused before any data is read. For the full site-wide view, the review queue in Confluence settings is the right surface- it covers every page in your audited spaces.

No. The rovo-ignore marker is advisory: StagBane's own agent and reader badge honor it, but native Rovo is unaffected, because Atlassian ships no native per-page exclusion mechanism. For hard exclusion, restrict the page's permissions natively- that is the only mechanism that actually removes a page from Rovo's reach. StagBane's queue can deep-link you straight to that native restrict-page flow.

Every audited page lands in one of four bands:

• Critical- no owner, no current review, and over a year old. Nothing is vouching for this page. Review first.
• Stale- likely out of date. A review lapsed, it is over a year old and never reviewed, or it links to pages that no longer exist.
• Watch- a supporting risk signal is present but not yet alarming, for example aging with no owner, or recently verified but now has a broken internal link.
• Healthy- no risk signal fired. This is not a guarantee the content is correct- it means the deterministic signals are clear.

There is no numeric health score. StagBane uses an explicit, ordered rule set- first match wins. The first rule that matches a page wins, and that single rule is shown in the queue alongside a one-sentence reason. A few compound rules escalate a page to Critical when problems stack- for example a stale page that also has broken links- and an unanswered review request can escalate an at-risk page past a configurable window, but each is still a single, plainly-stated rule.

Because of this, every banded page can answer "why is this page here?" with a short, literal sentence- not a composite number that blends multiple factors.

Every band is computed from five signals: age (fresh under 180 days, aging 180–365 days, old over 365 days), owner presence, review state (whether someone marked the page Verified Current within the review window), orphaned (whether any other audited page links to this one), and broken internal links (whether the page links to audited pages that no longer exist). The orphan and broken-link signals cover only pages within your audited spaces- a link crossing into a space you didn't audit is invisible to StagBane.

The age thresholds (fresh/aging/old) are fixed in v1 and not configurable. A few other settings are admin-configurable: the review window (30–1095 days, default 365- how long a Verified Current review stays current), the Request Budget (the daily cap on owner review comments, default 25, adjustable 1–100), the request-escalation window (1–90 days, default 7- how long an unanswered review request waits before an at-risk page escalates to Critical), and which columns the queue shows. There is still no numeric score and no configurable scoring. See the user guide for the full settings reference.

At the top of the queue, StagBane surfaces a short list of pages that are banded Healthy or Watch by the rules, but whose titles suggest they may be dated- a past year like "2023," or words like "draft," "legacy," "deprecated," "archived." This list nominates pages worth a human or agent read; it does not judge freshness itself.

An admin-only view, per audited space, of the band distribution plus a headline "Rovo-trustworthy %"- defined transparently as the Healthy share of monitored pages in that space. It is a coverage figure, always shown together with its per-band counts, never a per-page score. Site admins can see it in the queue or ask for it directly in Rovo chat.

Its capabilities fall into three categories: read-only audits, confirm-to-act actions, and admin-only views. In a normal conversation you'll mostly use the three read-only audits- audit one page (judges whether its content still looks accurate), compare two pages (judges whether they contradict each other), and find overlapping pages (searches for candidates on the same topic and offers to compare them). On your explicit confirmation it can also trigger the queue's non-destructive actions (see "Does the agent change the band of a page?" below), and site admins can ask for the ranked stale list or a space's Rovo-readiness view. Try asking it "Is this page still accurate?" or "Do these two pages contradict each other?" in Rovo chat.

The agent reads as you- it uses your Confluence access, not elevated app permissions. It can only see pages you can already open in Confluence. It holds no privileged access of its own. Every verdict cites the specific text behind its judgment and names the page version it read. Verdicts are chat-only and are never stored.

No. The agent reads as the asking user, using Forge's user-scoped access API. It can never surface content you don't already have access to in Confluence.

No. Everything the agent says is chat-only. Verdicts are never written to the review queue, the database, or anywhere else. Each question starts fresh.

The agent's verdict never changes a band- bands come from the deterministic rules, and a verdict is advisory and chat-only. If you explicitly ask the agent to mark a page Verified Current or Stale, that does re-band the page- but only because it triggers the same deterministic action a queue button does, on your confirmation and on your own permissions. The agent never persists its own judgment as a band, and never edits Confluence content. See the Rovo agent guide for more.

The agent uses your Rovo credits, like any Rovo agent- each question spends credits. Rovo credits are part of your Atlassian Rovo subscription, not the StagBane subscription.

No. StagBane is built 100% on Atlassian Forge and makes no external network calls. There is no developer-controlled server for your content to be sent to. Your content never leaves Atlassian. The Rovo agent's reasoning runs on Atlassian's own Rovo platform, using your Rovo credits, inside Atlassian's infrastructure.

No. The scanner reads page body content only to extract internal links. After links are extracted, the body is discarded and never stored. What is stored is page metadata, computed signals and bands, page-to-page link relationships, scan status, the review-request log, and the needs-review worklist flag- all in a Forge SQL database inside Atlassian, one isolated database per installation.

No. StagBane records no usage analytics of any kind.

No. StagBane does not require, request, or use any user's Atlassian Personal Access Token. All access happens through Forge's permission model and, for the agent, the user's own Confluence access.

The scanner indexes restricted pages the same as any other page. The admin-only review queue can show site admins the title, owner, and staleness signals of a restricted page- it never shows body content. This is deliberate: the queue is gated to site admins, who already hold latent access to restricted content on their site, and the exposure is limited to title, owner, and signals. The Rovo agent applies a stricter rule- it reads as the asking user, so it can never surface a restricted page's content to someone who couldn't already open it.

Labels (verified-current, needs-review, pha-evergreen) and any Review Request footer comments that StagBane added to your pages remain on those pages after uninstall- they belong to your content. Remove them manually if you no longer want them; they are ordinary Confluence labels and comments.

StagBane's own stored data- the Forge SQL database holding metadata, bands, link relationships, the review-request log, and scan status- is soft-deleted at uninstall under Atlassian's Forge hosted-storage data lifecycle. For a limited window after uninstall (21 days, per Atlassian's current policy), a reinstall can relink to the prior data.

StagBane is a single paid edition at about $1 per user per month, with a floor of about $10 per month at the 1–10-user bracket. A standard 30-day free trial is included through the Atlassian Marketplace. There is no free edition. The Atlassian Marketplace listing is always the authoritative current price.

No- StagBane is a paid app with a 30-day free trial. There is no free edition.

Yes. A standard 30-day free trial is available through the Atlassian Marketplace.

Confluence Standard or above. StagBane works on the Standard plan- Confluence Premium is not required.

Email support@stagbane.com or visit the support page. When you contact support, include your reference id (cid) if you have one- if an error occurred in the StagBane queue, the settings page shows a small line with the reference id of the most recent error, and an agent error reply includes one too. Including this reference makes it faster to find the exact event in the logs. See the support page for full details on what to include and what to expect.

Uninstall through your Atlassian admin panel, the same as any Marketplace app. See Privacy for what remains on your pages and what is removed.

No. StagBane is a Confluence Cloud app only. It is built on Atlassian Forge, which is a Confluence Cloud platform. It does not support Confluence Data Center or Server.