1. Scan impact
Enter one exact group name and run a read-only scan across supported Jira configuration surfaces.
Read-only Jira Cloud access audit
Know where a Jira group still affects access before cleanup.
Group Impact Audit for Jira is a read-only analysis app for Jira Cloud. It scans project roles and permission schemes, surfaces blockers and severity, and produces evidence you can verify later.
The first answer is practical: where the group still matters, how severe those references are, and whether cleanup should stop until they are reviewed.
How it works
Scan, review, export, verify.
The launch scope is deliberately narrow so the output stays legible and defensible in real admin workflows.
2. Review blockers
See blocked findings, severity, and readiness in one audit-oriented view before cleanup starts elsewhere.
3. Hand off proof
Save the run, export the evidence pack, and verify it later instead of relying on screenshots or memory.
Capabilities
One product, one outcome.
The app is designed around one coherent job: understand group access impact before deletion or cleanup.
Supported scan surfaces
Project roles and permission schemes for exact group-reference analysis at launch.
Operational review
Findings, severity, readiness, baselines, and snapshot comparison stay in one evidence model.
Governance controls
Policy rules, exceptions, drift visibility, and top-risk review support ongoing operational control.
Export and verification
ZIP, CSV, PDF, manifest, and verification workflows make the result reviewable after handoff.
Trust and scope
Read-only behavior is the product's center of gravity.
It helps admins understand impact before they change Jira. It does not make those Jira changes for them.
Included now
- Project role references
- Permission scheme references
- History and clean baselines
- Snapshot comparison
- Evidence export and verification
- Policy rules, exceptions, and admin safety controls
Explicit boundary
- No Jira permission, group, user, role, or scheme mutation
- Out of scope: workflows, filters, dashboards, issue security schemes, notification schemes, automation rules, and app-specific permissions
- Scheduling is interval-based at launch
- Jira API references can persist briefly after real cleanup changes
Demo and screenshots
Built to be reviewed, not just observed.
The interface is optimized around a workflow: scan one group, inspect blockers, compare state over time, export proof, and verify the result later.
- Overview and findings screen for first-pass review
- History and baseline states for comparison workflows
- Evidence metadata and verification flow for audit-ready handoff
- Explicit admin safety controls around stored data
Launch model
Simple commercial packaging.
At launch the product uses one public package, one full-featured trial, and Atlassian-managed checkout.
Paid via Atlassian
Customers evaluate and purchase through Atlassian Marketplace.
30-day full trial
Every feature is available during evaluation.
One paid package
No public free tier and no external starter/pro/enterprise ladder.
Marketplace bands
Use Atlassian Marketplace for the live per-user-band price table at launch and checkout.
Documentation and trust surface
Everything public, linked, and ready for review.
The product page is not the only surface. Support, guide, FAQ, privacy, terms, and security details are already split into public pages.
Guide
Install flow, scan behavior, severity meaning, evidence verification, and scope limits.
Support
Contact path, response targets, and the ticket details needed for triage.
FAQ
Short answers about scope, stored data, baselines, policies, and proof handling.
Security
Read-only posture, data handling summary, incident reporting path, and trust notes.