Documentation — Offboarding Auditor

Quick start

• Install Offboarding Auditor for Jira
• Open Jira administration
• Open Offboarding Auditor
• Run or wait for a scan
• Review inactive-user cases
• Inspect assignee/reporter dependencies
• Export audit evidence where required

Permissions used

Validate the listed scopes against the actual deployed Forge manifest before Marketplace publication.

• read:jira-user — Used to identify Jira users and determine whether accounts are active or inactive.
• read:jira-work — Used to query Jira issues for supported assignee and reporter dependencies.
• storage:app — Used to persist app configuration, scan state, findings, cases, history and audit metadata.

Product screens

• Overview — Summary of scan status, cases, dependencies and coverage.
• Cases — Inactive accounts grouped for offboarding review.
• Dependencies — Jira issues where the inactive account is assignee or reporter.
• History — Historical scan and review information.
• Audit export — CSV / JSON export and audit integrity metadata.

Known limitations

The current release only detects Jira issue assignee and reporter dependencies.

It is not a complete IAM, HR offboarding, or ownership-discovery platform.

If a user is missing

• verify the Atlassian account is inactive
• verify the issue actually references that account
• verify Jira permissions allow the app/user to access the issue
• rerun the scan

Uninstall

Uninstalling the app triggers app-managed cleanup logic (subject to verification in the released build).

Underlying Jira issues and Atlassian accounts are not deleted or modified by uninstall.