Audit over-broad Jira permissions and track configuration drift before enabling Atlassian Rovo or MCP — running 100% inside your Atlassian Cloud boundary.
Marketplace listing (App ID: 3567210724) is currently in review (submitted Nov 18, 2026). The direct app link will be published here once approved.
Jira Admin Page: Permission risk findings and structural configuration diff tracking.
When AI assistants such as Atlassian Rovo or MCP integrations are enabled, they inherit existing user permissions. Misconfigured permission schemes — such as anonymous access, all-logged-in-user grants, or overly broad default groups — can silently expose sensitive projects and issues.
Evaluates all Jira Permission Schemes and linked projects against governance rules:
anyone access.applicationRole.jira-software-users, jira-servicemanagement-users, jira-core-users, users, and confluence-users holding critical permissions.Captures deterministic snapshots of permission schemes, project mappings, and workflows, then computes exact structural diffs:
Includes a daily Forge scheduledTrigger with async queue processing (audit-scan-queue), plus manual scan execution directly from the Jira Admin Page (Permission Hygiene & Config Diff Auditor).
| Property | Implementation |
|---|---|
| Hosting | 100% Atlassian Forge (Node.js 24 runtime, Forge SQL MySQL). No external servers. |
| External Egress | None. Jira configuration and audit data never leave your Atlassian Cloud environment. |
| OAuth Scopes | read:jira-work, read:jira-user, manage:jira-configuration |
| Jira API Usage | Read-only Jira REST API v3 endpoints for permission schemes, projects, and workflows. |
No. The auditor is strictly read-only on Jira configuration. It surfaces prioritized findings and diffs so administrators can review and remediate safely.
ADMINISTER_PROJECTS, BROWSE_PROJECTS, EDIT_ISSUES, DELETE_ISSUES, DELETE_ALL_ATTACHMENTS, and MANAGE_SPRINTS_PERMISSION.
Reach out with your Jira Cloud questions or feedback.
Email [email protected]