UnitlaneJira cleanup tools
Short answers about estimates, cleanup candidates, Admin API token requirements, read-only group scanning, and coverage limits.
Decision map
Fast answersNo savings guarantee. No safe-to-delete guarantee. License Guard for Jira License Cleanup does not require Atlassian Admin API tokens for the default scan. Group Cleanup Radar is read-only. Coverage labels show covered, partial, unavailable, and manual-check sources.
No. It estimates next-cycle or renewal impact based on assumptions and selected cleanup candidates. The estimate gives finance and admins a useful planning range, but actual billing impact depends on plan, contract, timing, and selected changes.
No. It means no detected references were found in covered sources. It is a triage label, not deletion approval. Review detected references, partial coverage, unavailable sources, and manual checks before changing Jira.
No. It does not delete, rename, modify permissions, edit workflows, or change Jira configuration. The product is designed for review and evidence. Jira group deletion, rename, permission edits, and workflow changes happen outside the read-only scan.
No. Start with the scan. Approval and proof workflows are available when needed. The first useful action is the scan. Approval and proof steps are available later when another admin, finance reviewer, or audit trail needs them.