Mastering Jira Cloud: A Guide to Optimizing Productivity with Different Access Levels

[#1]

Many Jira Cloud users often find themselves uncertain about the different levels of access that are available to them. Atlassian/Jira Cloud provides distinct levels of access: Organization Administrator, site administrator, Jira Administrator, project administrator, and team member(user). In this article I will talk about what activity/action can be performed by the particular access level available in Jira cloud.

Organization Administrator: As an Organization Administrator, you have access to the admin portal at admin.atlassian.com where you can manage your organization. Some of the actions you can perform include.

• Granting other users organization admin permissions to assist with management tasks.
• Verifying or removing domains associated with your organization.
• Subscribing to Atlassian Access to apply security policies on managed accounts.
• Managing user accounts within your organization, including editing details and deactivating or deleting accounts.
• Access the audit log to review user and admin activities within your organization's Atlassian Cloud products.
• Review and manage billing and subscription information for your organization's Atlassian Cloud products.

Site admins can perform these site operations:

• Access the site's Admin at https://admin.atlassian.com.
• Make other users' site or product admins.
• Site settings so that it displays your company's branding and image.
• Administer users for your site, meaning you can invite, remove, and export users, among other things.
• Groups and product access, meaning you can update settings for how users get access and adding users to groups.

Jira Admin:

• Manages the Jira Cloud instance as a whole, including all projects within it.
• Configures Jira Cloud settings, such as global permissions, system settings, time tracking etc.
• Responsible for managing add-ons and integrations with other tools used by the organization.
• Customizes Jira Cloud by creating custom fields, issue types, workflows, and screen schemes.
• Maintains and manages Jira Cloud data, backups, and restores.
• Provides technical support to Jira Cloud users and resolves technical issues related to Jira Cloud

Project Admin:

• Manages a specific project within Jira, including creating, editing, and deleting issues within that project.
• Manages project settings, such as project boards, workflows, etc.
• Responsible for managing project permissions, including granting access to team members and controlling what actions they can perform within the project.
• Configures project-specific reporting and dashboards to track project progress and performance.
• Collaborates with team members and stakeholders to ensure project goals are met and project delivery is on time and within budget.
• Acts as a point of contact for project-related queries and concerns.

Trusted User:

• A trusted role is a type of privileged role that has more permissions than basic users but fewer permissions than a site administrator.
• Trusted users have access to all products on the site and can perform administrative tasks.
• Trusted users can invite new basic users to the site
• Trusted users are automatically granted a product license for all products on the site when assigned the trusted role.
• Trusted users can invite new basic users to any products on the site without requiring site admin approval.
• Trusted users can administer site products, add new products to the site, and add apps to the site.

Jira User:

• Create, view, edit, and comment on issues within a project.
• Add attachments and screenshots to issues.
• Use Jira filters to search and filter through issues.
• Create and save custom filters to access frequently used searches.
• Create and save custom dashboards to display important project information.
• Assign and transition issues through various workflow statuses.
• View project statistics and reports to track project progress.
• Mention and tag other users within issues and comments.
• Manage personal profile settings and preferences.
• Collaborate with team members by sharing and delegating issues.
• Use Jira Agile boards to plan and track sprints, epics, and versions.

In conclusion, Jira Cloud offers multiple levels of access to its users, including Organization Administrator, site administrator, Jira Administrator, project administrator, and team member(user). Each level of access provides a unique set of functionalities to perform tasks related to managing the organization, site, project, or specific issues within Jira Cloud. By understanding the available levels of access, Jira Cloud users can effectively manage their projects, streamline workflows, and ensure efficient project delivery.

[Mayur Jadhav]

Please feel free to add if i have missed anything. 

Thank you!!

[Tomislav Tobijas]

Nice article! What I've seen at some of our clients' sites is that it can be tricky to distinguish the difference between the Org admin and Site admin. It usually appeared to be the same thing.

Also, it might be worth mentioning that changes to user roles should be rolled out from mid to end of 2023: https://community.atlassian.com/t5/Atlassian-Access-articles/Say-hi-to-our-new-user-admin-role/ba-p/1890277

[Mayur Jadhav]

@Tomislav Tobijas  When you don't have Atlassian access enable then the Site Admin and Org Admin both are same. You will see the actual differences after enabling the Atlassian Access.

[Kavya Singh]

Very Informative, Thanks for sharing @Mayur Jadhav 

[Yatish Madhav]

Thanks for this @Mayur Jadhav  - agree with @Tomislav Tobijas  - the user admin role changes this post a bit. But a great article none the less. Thank you