NF / Docs / License Radar
Getting started with License Radar
Run a read-only Jira access review and understand the evidence before renewal.
Last updated: 2026-09-08
In this section
What License Radar does
License Radar for Jira helps site administrators decide which Jira access deserves a closer look before renewal. It reads supported Jira application-role access and observable issue-update activity, then turns that evidence into review candidates and transparent cost estimates.
It is a review tool, not an access-removal tool. License Radar never removes or suspends users, changes groups, revokes access, edits permissions or changes billing.
What you need
- A Jira Cloud site where License Radar is installed.
- Jira site-administrator access.
- A review threshold and, for Pro, the cost assumptions you want to use.
The installed Jira site is detected through Atlassian Forge. You do not need to enter an Atlassian password, API token, OAuth secret or service-account credential.
Your first review
- Open License Radar from the installed Jira site as a site administrator.
- Read the access and activity scope shown in onboarding. The activity signal is based on Jira issue updates visible through the supported APIs; it is not an organisation-wide login metric.
- Run the first read-only scan. Wait for a
COMPLETEDresult before treating the totals as current. - Start with the estimated annual cost associated with access worth reviewing, then open the strongest candidates.
- Open Candidate Evidence for each decision. Check the observed activity, threshold, product access and evidence coverage before reviewing access outside Jira.
Keep the result in context
“Review candidate” means the available evidence merits administrator attention. It does not prove that a person never used Jira, that the access is unnecessary or that a charge will disappear from an Atlassian invoice.
If the scan is PARTIAL or FAILED, License Radar shows the limitation and does not turn unavailable activity into a zero-activity result. See Running a scan and Troubleshooting.