License Guard Guide
Guide

What the app does, what it exports, and where the boundaries are.

Use this guide to understand the review workflow, supported cleanup model, proof exports, and what remains intentionally out of scope at launch.

Getting started

  1. Install the app from Atlassian Marketplace when the public listing is live.
  2. Open the app through Jira Settings and run the first governance scan.
  3. Review the current queue and inspect why each seat is still billable.
  4. Approve or reject the staged batch before cleanup runs.
  5. Use the Proof page to review export readiness and evidence after each cycle.

Supported scope

  • Inactive and never-used seat detection
  • Group and product access-path explanation
  • Dry-run review, approval, and rejection flow
  • Protected exceptions and held-out rows
  • Proof exports in CSV and JSON
  • Weekly or monthly scheduled scan cadence
Workflow

The product is organized around one decision sequence.

Review state is kept stable so admins can explain the decision later instead of reconstructing it from memory.

Step What it tells the reviewer
Overview Current batch state, billable rows by lane, proof posture, spend estimate, changes since the previous cycle, and scheduled-scan state.
Review queue Which rows are ready for approval, which need manual review, why the seat is billable, and which groups or products are attached.
Approvals Whether the current batch is awaiting decision, approved, or rejected, together with notes and execution readiness.
Proof Whether exports are preview-only or backed by execution, and whether the latest cycle can be treated as final evidence.

Exported artifacts

  • CSV evidence export
  • JSON evidence export
  • Execution and action history tied to the exact cycle
  • Decision notes, actor identity, and timestamps

What stays out of scope

  • Deletion or deactivation of Atlassian user accounts
  • Replacement for SCIM, IdP provisioning, or broad user-management suites
  • Bitbucket cleanup and arbitrary Atlassian products outside the currently modeled product set
  • General Jira administration consulting outside the app