Site Admin role

Ivonne Terrero_ibixn6

I'm prepping for my ACP-520 and I'm in trying to understand what the site admin has the ability to do and not to do. I'm looking at this page 

https://support.atlassian.com/user-management/docs/what-are-the-different-types-of-admin-roles/

but I'm confused between these two statements: 
 

1) Site admins can't manage product access for the sites they administer
2) Site admin can approve or deny request to access products for the sites they manage. 




If a Site admin can approve or deny requests to access products for the sites they manage. How come they can not grant existing users access to Jira software on the site they manage? 

 

Can someone please explain how these two are different. 

Thank you!

Kavitha Chandrasekaran

Hi @Ivonne Terrero 

To break it down a org can have multiple sites. 

Each site can have one more more products, installed apps etc. 

In large organisations, it may be hard for org admin to manage multiple sites. So site admin role with help manage the site. 

1) Site admins can't manage product access for the sites they administer
2) Site admin can approve or deny request to access products for the sites they manage. 

Point 2 comes via invitation links etc.

Site admins can approve/deny requests. This is more like an administrative task. The site admin might be given a guideline of who to approve by default (like if email orginates from the company domain etc.)  

Point 1. Site admin cannot go to the list of users for the site and remove a user from a product access (example Jira) or go ahead and add a new user to a product. 

Hope this helps. 

I did my ACP-520 early this year and have some notes that I shared to Atlassian Community. This includes some good links from other people too. 

https://community.atlassian.com/t5/Training-Certification/ACP-520-Atlassian-Cloud-Organization-Admin-Certification-Journey/td-p/2526292