Hi,
I'm currently preparing for the ACP-610/ACP-620 certification, and I have been going through the lessons in Managing Jira Projects (ACP-610/ACP-620 Certification Prep) a few times, and I've also been reading random blog posts and discussions on the Atlassian community. My previous experience with Jira software is as an end user.
I've found it difficult to fully grasp the terminology surrounding the levels of administration for Atlassian/Jira, and I believe this is due to inconsistencies in the terminology used on forums and in the Atlassian University course material.
I'd like to discuss what I have found so far, probably exposing my lack of knowledge and getting slapped on my fingers for ranting about stuff I just learned.
The terms for describing different levels of administration that I have come across are:
From what I have found, Organization admin and Site admin have the same permissions. The difference is that Organization admin is a role and Site admin is a group. After plaiying around in the sandbox supplied via the certification course, I noticed this:
Furthermore, the Jira admin and the Product admin relate to each other in a similar way;
This has given me the impression that there are essentially three levels of administration in Jira:
Is this a correct assumption?
Thanks,
Johan
Thanks for your reply!
So if MyCompany is the org, and I'm the Org admin and you're the site admin, we initially both have the same perminssions (apart from billing details) at MyCompany.atlassian.net?
We both have access to admin.atlassian.com and MyCompany.atlassian.net, right?
And if I'd create another cloud site MyCompanySweden.atlassian.net only I could access that site, and you could only access MyCompany.atlassian.net until made site admin for the new site?
Appreciate you taking time to help me!
Right. As an org admin, you add site admins to your different sites by putting them in the appropriate site-admins group.
Not quite - in Jira, there are four levels. But there's also only three. Yes, I've just directly contradicted myself, but it's not a Schroedinger's cat problem, it's a visibility thing.
When you've seen "product admin", it means "Atlassian product admin", and when you're looking at Jira, that might mean "Jira system admin" or "Jira admin" depending on the context.
The levels in Jira are:
But, it's three because:
Server/DC does not have "site admin", because there is no "site" when you're running it yourself. Your network and application admins take on the stuff site admins do on Cloud (access, authentication setup, user provisioning etc). It only applies to Cloud. So there are only three layers you can get to as a Jira admin.
On Cloud, technically there are four layers in the system, but you, as the end-user, do not get system admin. Only Atlassian can do system admin. So there are only three layers you can get to as a Jira admin.
Hi,
In server we have:
System admin
Jira Admin
Project Admin
in Cloud we have:
Organization Admin
Site Admin
Product Admin
Project Admin
However the Jira admin in server is extended to organization admin, site admin and product admin in Cloud & Project admin in server is extended to project admin in cloud with team managed project.
I hope you're in the timeline where I posted this comment to thank you for your help!
Recommended Learning For You
Level up your skills with Atlassian learning
Learning Path
Jira Administrator
Configure Jira Software, Jira Core, or Jira Service Management, including global settings, permissions, and schemes.
Managing Jira Projects Cloud
Learn to create and configure company-managed projects in Jira Software and partner effectively with Jira Admins.
Learning Path
Become an effective Jira Software Project Admin
This learning path is designed for team leaders who configure Jira Software projects to match a team's processes.