Security guide

Jira anonymous access

Jira Cloud can show a space, a filter or a dashboard to people who are not logged in. Sometimes that is on purpose, such as a public roadmap. Often it is a setting someone changed years ago and forgot. Here is what the two broad grants expose, where to check each by hand, and how to fix them.

Published 16 November 2026 · Jira Cloud · A practical guide, not legal advice

What the two broad grants mean

Holder, as Jira shows itWho that isHow serious
PublicAnyone on the internet, without logging in (anonymous access)Fix first
Any logged in userEveryone who can log in to the siteCheck intent

Public means no login at all: a person with the link can use the permission. On the browse permission of a space, that is every work item in it: summaries, descriptions, comments and attachments. On a filter or a dashboard, it is whatever that filter or dashboard lists.

Any logged in user is narrower but still wide: everyone with an account on your site, whether or not they work on that space.

Treat the first as a possible leak to the internet and the second as a question: is it right that everyone with an account can read this? Either can be correct. The risk is a grant nobody remembers making.

Names changed. Jira Cloud now calls projects spaces and issues work items. This guide uses the new names. If a menu path below does not match your screen, use the search box in Jira settings.

A one-minute test

Copy the link of a work item, a filter or a dashboard, and open it in a private browser window, where you are not logged in. If you see the content instead of a login page, it is public. This proves one link only; the checks below find the rest.

1. Permission schemes: the browse permission

  • Check: Settings (the gear icon) → Work items → Permission schemes. Open each scheme and find the permission to browse the space. Look for Public and Any logged in user among its holders. Then see which spaces use the scheme: one scheme can open many spaces.
  • Fix: edit the scheme, remove the broad holder, and grant the permission to a space role or a named group instead. Check the same two holders on the other permissions too, especially creating and editing work items and administering the space.

2. Shared filters

  • Check: Settings → System → Filters. Look for filters shared publicly or with all logged-in users. A shared filter only leaks if its query returns work items the audience should not see, so open each flagged one and read what it returns.
  • Fix: the filter's owner changes the sharing from the filter's details: replace the broad share with a space, a role or a group. Admins can change a filter's owner or delete it from the same list, which helps when the owner has left.

3. Dashboards

  • Check: Settings → System → Dashboards (under Shared items). The search shows each dashboard's owner and who it is shared with. Look for dashboards shared publicly or with all logged-in users, and for dashboards whose owner has left. Gadgets can list work items, names and counts.
  • Fix: narrow the sharing the same way, or change the owner first so someone is responsible for it.

What to keep

Write down the date, what you checked, every broad grant you decided to keep, and who owns it. Re-check after a fix, and again on a schedule: a broad grant returns when a new space is given an old scheme. For the full review, with admin groups and space roles, use the Jira permission audit checklist; for audits, see the access review for SOC 2 and ISO 27001.

The same check on one page with Ledgerstone

Ledgerstone is a Jira Cloud app that runs these checks for you. It reads permission schemes, shared filters and dashboards, space roles and administrative groups, and puts the result on one page. Anything public is graded High, anything open to every logged-in user is Medium, and an area it could not fully read says Could not verify. Each finding links to the Jira page where it is fixed. The first audit runs when you open the app, then it runs by itself every week, and a "Since last week" card lists findings that appeared or were resolved.

  • Read-only: built on Atlassian Forge with read scopes only, so it cannot change anything in Jira.
  • Nothing leaves Atlassian: no network calls outside Atlassian. Only counts and configuration names are kept, not people's names.
  • Free for sites up to 10 users; then $1.50 per user per month, with a 30-day free trial.

Try Ledgerstone free on the Atlassian Marketplace, read how it works, or send us a message.

Spotted a menu that moved? Tell us and we will update this page.