Ever lost admin access to a Team Managed project?
As a Jira Admin, did you ever lose access to a Team Managed project with no way to know?
Team Managed projects have their own permission model that sits outside the usual admin hierarchy. If a project is private — whether it was created that way or a project admin changed it later — even Org Admins and Jira Admins lose access to its settings unless they're explicitly added to a project role.
That's why it's good practice to always keep your admin or Jira support group in the Administrator role across all Team Managed projects. The problem is that any project admin can remove it at any time and you won't know until something breaks.
That alone is easy to miss. You only find out when something breaks or someone reports it, and the only workaround is manually editing the URL to reach project settings.
I ran into this repeatedly and first solved it with a Jira Automation rule that queries the API to surface affected projects (happy to share that approach if anyone's interested)
But as I wanted something more accessible, I built a Forge app for it. And it's free.
You select any Jira group (e.g. jira-administrators) and instantly see which private Team Managed projects are missing it as Administrator. You can add the group back directly from the app. No URL hacking, no manual checks.
Remember: It's free, requires no external setup, and runs entirely within your Atlassian site.
Would love feedback from the community, especially from Jira admins who've hit this gap before.
🔗 Team Managed Audit
5 comments
Sorry, I forgot to mention that this happens only on "private" TM projects, which project admins can set as private.
Still cannot reproduce; one of our use cases is almost exclusively all team-managed projects of which most are set to private. I can still see all on the Mange Spaces screen and enter any, although it won't load the items within it.
When providing support, I can then easily get to the access page within a Space and give myself appropriate permissions without needing to manually manipulate the url.
Still cannot reproduce; one of our use cases is almost exclusively all team-managed projects of which most are set to private. I can still see all on the Mange Spaces screen and enter any, although it won't load the items within it.
When providing support, I can then easily get to the access page within a Space and give myself appropriate permissions without needing to manually manipulate the url.
