Cleanup-ready
Rows that look ready for access cleanup, separated from review and protected users so the first pass focuses on likely savings instead of a flat user export.
Separate cleanup-ready, needs-review, and protected users before action.
License Guard for Jira License Cleanup keeps cleanup lanes explicit before action.
Rows that look ready for access cleanup, separated from review and protected users so the first pass focuses on likely savings instead of a flat user export.
Uncertain users stay visible so admins can inspect billable paths, external-management limits, and protected status before deciding what to preview or export.
Admin, service, app, or excluded rows stay out of the default cleanup lane, which keeps savings discovery separate from risky access changes.
It does not make cleanup automatic.
Uncertain users stay visible so admins can inspect billable paths, external-management limits, and protected status before deciding what to preview or export.
This point keeps the evaluation practical: what to inspect, why it matters, and what should remain a manual review before any Jira cleanup decision.
This point keeps the evaluation practical: what to inspect, why it matters, and what should remain a manual review before any Jira cleanup decision.
Continue to License Guard for Jira License Cleanup for the current screenshots, evaluation path, trust boundaries, and Marketplace trial link behind this workflow.