Permission Audit for Jira

by triangle-tech

works with Jira Cloud

OVERALL RATINGS
INSTALLS
SUPPORT: Partner Supported
TRUST SIGNALS

Showing details for Cloud

Overview

Reviews

Pricing

Privacy & Security

Support

Installation

Similar Apps

New

Key highlights of the appFind risky public, group, role, and admin grants across every Jira project

Find the highest-risk permissions first

Run 26 read-only checks across Jira permission schemes and rank every finding by severity, weighted risk score, and project impact.

Prioritize cleanup across projects

See which projects, groups, roles, and finding types contribute the most risk, so administrators can focus remediation where it removes the most exposure.

Prove every change with audit history

Compare each scan with the previous one, track new and resolved findings, and review severity-weighted risk trends across up to 12 scans.

Supporting media

More details

Permission Audit 2.6 keeps the complete site-wide review workflow introduced in 2.5 while migrating persistent storage to Atlassian's supported Forge KVS interface. Existing storage keys and data formats are unchanged. Administrators can continue to run 26 read-only checks, prioritize remediation, compare scan changes, retain trends, schedule weekly scans, and export audit-ready CSV. English and Japanese UI remain available. Data stays inside Atlassian Forge, with no external network egress and no Jira write scopes.

Resources

App documentation
Comprehensive set of documentation from the partner on how this app works

Privacy and Security

Privacy and security questionnaire has been filled by the partner

Privacy policy

Atlassian's privacy policy is not applicable to the use of this app. Please refer to the privacy policy provided by this app's partner.

Partner privacy policy

Security program

This app is not part of the Marketplace Bug Bounty program.

Integration permissions

Permission Audit for Jira integrates with your Atlassian app

Version information

Version 2.6.0•for Jira Cloud

Release date: Aug 30th 2026
Summary: Supported Forge KVS migration with unchanged data and permissions
Details: Migrated app storage from legacy @forge/api storage to supported @forge/kvs.
Preserved existing scan history, accepted risks, storage keys, and value formats.
Added no Jira scopes, write permissions, or external network egress.
Payment model: Paid via Atlassian
License type: Commercial