Get started with Guardian.
Put a clearer view of configuration risk within reach. Start with the right Jira site, administrator access and a review of the permissions.
Install and open#
Guardian supports Jira Cloud. For the published release, use its verified Atlassian Marketplace listing, select the intended Jira site and have an authorized site administrator review and approve the installation permissions. An organization app-approval policy may require additional administrator approval. A public Marketplace listing is not yet available. Installation becomes available after the separate App release.
Open Apps → Config Health Guardian for Jira as a Jira administrator. Pages are Overview, Findings, Scan history, Coverage and Settings. If the app is absent, confirm that installation completed on this site and that an administrator approved any pending permission update. Installing on one site does not install on every site in an organization.
Permissions#
Every app request checks the caller's current Jira ADMINISTER permission. Jira and Jira Software scopes read supported configuration and validate JQL; they do not permit Guardian to edit Jira configuration. storage:app stores Guardian's own records, and report:personal-data reports stored account identifiers and observation times to Atlassian for privacy handling. The masking-enabled manifest has 30 scopes, including read:screen:jira and read:screen-tab:jira for the existing field-screen lookup. These read scopes do not add an advertised Field Screen Evidence feature. See Security and Data for scope categories, masking rollout status and the data lifecycle. Declining required permissions can prevent operation or leave Coverage unavailable. Installation does not guarantee access to every Jira product/domain.