StagBane- Quick Start

This is the fastest path from installing StagBane to seeing it find a real problem in your own Confluence. It's written for a Confluence site admin doing their first run.

Budget about 15 minutes, most of which is waiting for the first scan to finish. By the end you'll have a ranked queue of your stalest pages and will have acted on one.

Before you begin

You are a Confluence site admin (the review queue is admin-only).
You're on Confluence Standard or higher.
Rovo is optional. The review queue works without it; you only need Rovo enabled (with credits) for the Audit steps, where the Page Health Auditor reads page content.

Step 1- Install and open

Install StagBane from the Atlassian Marketplace.
Go to Confluence → Settings → StagBane.

Step 2- Pick one or two spaces to audit

On first run, choose your audited spaces. StagBane scans nothing until you do.

Choose your most-used, most-trusted spaces- the team handbook, your policies, your runbooks. Leave personal and archive spaces out for now.

Tip: Start with one or two spaces, not everything. You'll reach a useful queue faster and won't drown in day-one noise. You can add more spaces anytime.

Step 3- Let the first scan run

The first scan reads every page in those spaces once to build its link map. The status line at the top of the queue shows progress; a large space takes longer, so you can leave and come back.

What this means: this full read happens only once per space. After it, the daily scan only re-reads pages that changed, so it's fast.

Step 4- Read the Critical band (this is the payoff)

The queue opens with the most urgent pages first. Look at the Critical band.

A page is Critical when it has no owner, no current review, and is over a year old- nothing and nobody is vouching for it, yet your team and Rovo may still be treating it as true. That gap is exactly what StagBane exists to surface.

Band	Read it as
Critical	Review first- unowned, unreviewed, and over a year old.
Stale	Likely out of date- a lapsed review, very old and never reviewed, or links to deleted pages.
Watch	Worth an eye- a supporting risk signal, but not yet alarming.
Healthy	No risk signal fired. (Not a guarantee the content is correct- see Step 6.)

Example. A page like "Onboarding- Legacy VPN Setup," last edited two years ago, whose author has left the company and which no one has ever reviewed, lands in Critical. It's precisely the kind of page you want out of Rovo's reach.

Every row names the one rule that placed the page there and a one-sentence reason, so "why is this here?" always has a short answer.

Step 5- Act on one page

Pick a single page from Critical (or Stale) and choose the move that fits. None of these delete or archive anything- every action is reversible.

Mark Current - you checked it and it's still accurate. Records today as its review date and moves it toward Healthy on the next scan.
Request Owner Review - someone else is the right person to judge it. Posts one comment that @mentions the page's owner and asks them to reply Verified or Stale to resolve it without leaving Confluence. A daily budget (25 per site) means this can never become a notification storm.
Audit - you're not sure whether the content is stale. Opens the Page Health Auditor in Rovo chat, aimed at this page. Try: "Is this page still accurate?" It reads the page, cites the text behind its judgment, and names the version it read.

The agent can also act and answer site-wide. After it reads a page you can ask it to "mark this current" or "ask the owner to review it"- it confirms first, then triggers the same non-destructive actions as the queue. Site admins can also ask "which pages are stale?" for the ranked list in chat. Full details in the Rovo agent guide.

Step 6 (optional)- Catch stale pages that look healthy

At the top of the queue, open Worth a closer look. These are pages the rules rate Healthy or Watch, but whose titles hint they may be dated- a past year like "2023", or words like "draft" or "legacy".

Click Audit on one. This is the second payoff: a page the queue calls Healthy on a fresh timestamp that the agent reads and tells you is actually out of date. (This step needs Rovo.)

Quiet the noise (30-second tune-up)

Apply the pha-evergreen label to any page that is old on purpose- a frozen policy, an archive index. StagBane stops banding it and moves it to the Excluded view.
Leave the Request Budget at its default of 25 unless you're doing a big one-time cleanup. It's the guardrail that keeps review requests from spamming owners.

You've seen the value- what's next

User guide - the complete reference: every signal and band rule, all four actions in detail, the Rovo agent's full capabilities and limits, and troubleshooting. See its first-week workflow for the ongoing rhythm after this first pass.
Privacy & data - exactly what StagBane reads, what it stores, and what happens on uninstall.

Questions: support@<your-domain>.