Reading candidates and evidence

Start with the review opportunity

The overview prioritises:

• Jira access analysed.
• Review candidates.
• Strong candidates.
• Estimated annual cost associated with access worth reviewing.
• Scan coverage and the last successful scan.

The economic figure is a modelled opportunity, not a confirmed saving. It combines visible access, the configured price assumption and the candidate classification for a completed scan.

Candidate classifications

• Strong candidate — the available activity evidence is substantially beyond the configured review threshold and no protection rule applies.
• Review recommended — the available evidence merits a closer look, but it should be checked with the relevant owner.
• Insufficient evidence — the activity signal is missing or the scan coverage is not sufficient for a recommendation.
• Protected — the record matches an administrator protection rule or other supported protection state.
• Recently active — the observable activity is inside the configured review window.
• Suspended — Jira reports the account as inactive or suspended; confirm the current administrative state in Jira.

The labels help organise review work. They do not prove intent, employment status, login history or a required access change.

Candidate Evidence

For each candidate, open Candidate Evidence and check:

• The observable Jira issue activity date, if one was returned.
• The review threshold used for the scan.
• The Jira access detected through application-role information.
• The estimated configured cost, shown with an estimated label.
• Evidence coverage and the scan status.
• Whether protection or exclusion rules apply.
• The access-path limitation. Group membership may be visible, but License Radar does not claim that a group caused product assignment when the Jira API did not prove that relationship.

The product can explain why a record deserves review. It cannot provide an organisation-wide last-login metric or a guaranteed answer to “who never used Jira?”.

Costs and currency

Free uses transparent reference pricing. Pro can use administrator-provided costs or a configured total monthly spend. Amounts are annualised or monthly as labelled and rounded for an estimate. They do not include discounts, contract terms, taxes or the final Atlassian invoice unless you supplied an assumption that accounts for them.

Use the phrase estimated cost associated with access worth reviewing in internal reports. Do not describe it as money already saved.