MetaFrazo Sentinel
Runs on AtlassianOverview and how it works.
An access review and permission audit for Jira Cloud, with no external server and no data leaving Atlassian.
What it is
MetaFrazo Sentinel is an access review and permission audit for Jira Cloud. It shows who can access what across your projects, who changed permissions and when, and lets you sign off a review with a record of exactly what was signed. It Runs on Atlassian: all processing and storage stay inside your Atlassian cloud, with no external server and no data leaving Atlassian.
How it works
- Install Sentinel from the Atlassian Marketplace and open it from Apps → MetaFrazo Sentinel.
- Decide who may use it. Jira administrators have full access. Regular users have no access. To give auditors read-only, site-wide access, grant the global permission “Sentinel: view access audit” to a group on Jira’s Global permissions page. To let project owners review their own project, grant “Sentinel: review project access” in that project’s permission scheme. Both are Jira’s own permission screens; Sentinel checks them on the server for every request.
- Run scan. Sentinel reads permission schemes, project roles and group membership across your projects and flags access that needs a decision: deactivated users who still hold roles, empty groups that are still granted rights, permissions open to anyone, broad administrator rights, and schemes shared across unrelated projects. Each finding explains why it matters and links to the Jira setting where you change it.
- Review and sign off. Mark each access grant Keep, Revoke or Investigate, then sign the review round. The sign-off records who signed, when, the counts, the signed findings with their decisions, and a sha256 fingerprint that is re-verified against them. Sign-offs are never edited; a correction is a new sign-off.
- See who changed permissions, and when. Permission changes lists changes to permission schemes, global permissions, project roles, groups, users, issue security and public access, plus projects that were deleted, archived or restored, read from the Jira audit log and kept beyond Jira’s own retention. It shows the date from which the record is complete.
- License & seats. Licensed users per Jira product, users with no recent activity, and candidates for seat reclaim; mark service accounts that are expected to be idle.
- Export. The findings CSV states when the scan ran, how many projects it covered out of how many, and anything missing. The change log CSV states its period and completeness. Each sign-off exports its signed content as CSV or prints to PDF.
Runs on Atlassian: private by design
Everything runs inside your Atlassian cloud on Atlassian Forge, in the region your Atlassian data lives in. There is no external server and no data leaves Atlassian. Sentinel reads Jira with read-only permissions and never changes it. It stores Atlassian account IDs, configuration names and the results of its own scans; never names, email addresses or issue content (names are looked up when a page is shown). Accounts deleted from Atlassian are anonymized automatically. Uninstalling deletes all Sentinel data, so export your evidence first.
Full terms, privacy, security and the DPA: Legal.
Requirements and permissions
- Jira Cloud. Paid via Atlassian, with a 30-day free trial.
- Jira Standard or Premium for Permission changes (it reads the Jira audit log, which Jira Free does not provide). The access review, sign-off and License & seats work on every plan.
- Scopes requested (all read-only):
read:jira-work(projects, permission schemes, project roles),read:jira-user(users and groups holding access),read:application-role:jira(Jira product access and seats),read:user:jira(licensed users and their status),read:audit-log:jira(the permission change log).
FAQ
How is this different from Atlassian Guard? Atlassian Guard secures the organization: identity, single sign-on, user provisioning and the organization audit log. Sentinel works inside Jira: which permission schemes, project roles and groups give whom access to which projects, who changed them, and a signed review of that access. They answer different audit questions and work well together.
Which Jira plan do I need? Any Jira Cloud plan for the access review, sign-off and seats; Standard or Premium for the permission change log.
Support
- Support portal: MetaFrazo support
- Email: support [at] metafrazo.cloud
- Hours: Monday to Friday, 09:00 to 17:00 CET/CEST, excluding public holidays.