Ascertaining number of admins

[Jim Stewart]

We are cutting over from Zendesk to Jira Service Desk. I was asked this question and wondered what was the fastest path to getting the answer (as below):

Can you please figure out how many admins are currently there for Atlassian/JIRA? What they see and what they can't and what if we can take away the broader access to them  etc 
The idea is to make sure others can't see the information that's sensitive like HR or Payroll etc. 

[Benjamin Paton · Accepted solution]

Hey Jim, 

There are a few different types of administrators. Site, Jira, and Project. Each have different permissions. 

A Site Administration can do almost anything, and see almost anything, you should only have enough of these to maintain your instance. 

A Jira Administrator has control over creating projects, managing workflows, and system based schemes. Again, you should only have a few of these, ideally limited to those who know what they are doing.

A Project Administrator looks after an individual project, they can configure the request types, queues, and settings for that project. Ideally you would have 1-3 per project.

You can filter for Site and Jira Administrators through the Settings > User Management menu. 

You can filter for Project Administrators within each individual project (Project Settings > People). Keeping the sensitive projects limited for both Administrators and Agents will help keep them private.

Here is some further reading on the topic :- https://support.atlassian.com/jira-service-desk-cloud/docs/overview-of-permissions-in-next-gen-service-desks/

Cheers, 

Ben.

[Jim Stewart]

That helps. I did filter on admin and got the results. However, not mentioned in your summary above is Org admin. Can you briefly describe the difference from the others? I suspect this is the most "dangerous" person in that he or she can do everything. But what can she do that the Site administrator cannot do?

[Benjamin Paton]

Sorry for the omission. 

An Org admin looks after a group of sites, they are responsible for cross-site users, billing, and overarching security settings.  Org admins should be the rarest of all.

This role has more capabilities when using the Enterprise edition of our products.