Operate Audit Policy Guard with clear boundaries.
Documentation for Jira administrators covering access, scanning, retained evidence, deletion, limitations, and support.
Built for Jira administrators.
Install Audit Policy Guard in Jira Cloud through Atlassian Marketplace when the listing is available.
The app page is visible only to users with Jira global administrator permission.
No separate Lumiprax account, external service account, or third-party credential is required.
Review policy-relevant administration changes.
Open Audit Policy Guard from Jira administration.
Select Run scan now to evaluate available Jira audit records immediately.
A licensed installation also runs the monitor on a five-minute scheduled trigger.
Recent findings show severity, generic policy information, source record ID, and event time for matching events.
Minimized evidence, hosted on Forge.
Jira audit records are processed transiently for deterministic policy classification.
Raw audit payloads, actor names, email addresses, IP addresses, object names, and before/after values are not intentionally persisted.
Matching findings are stored in Atlassian Forge KVS for up to 365 days; scan-status metadata is retained for up to 30 days.
Audit Policy Guard declares no external network egress and no Jira write, delete, or manage scopes.
Know what the app can and cannot report.
An authorized Jira administrator can delete stored findings from within the app, including when a commercial license is inactive.
Coverage is limited to events Jira records and exposes through its audit records API.
Audit Policy Guard cannot reconstruct changes that are absent from Jira's audit log.
Contact Lumiprax for product help.
Email support@lumiprax.com with the app name, what happened, what you expected, and relevant timestamps.
Do not send passwords, API secrets, access tokens, or authentication credentials.