Jira Image of the Day: Permission Levels

[#1]

Concept Relates To

Application Type	Jira Work Management, Jira Software, Jira Service Management, Jira Core
Deployment Type	Jira Cloud, Jira Server, Jira Data Center

What is shown?

A diagram showing multiple levels of Jira permission settings

What can we learn?

There are many levels of Jira permissions to be aware of and they all work together. They are:

Application Level

At the very highest level is application access. If the user doesn’t have application access, they can’t login and therefore no permission at any other level applies. Application access is granted in each user’s profile. The general application access groups are in the format jira-productname-users. Ex: jira-software-users, jira-servicedesk-users, etc. If your application is older, you may simply have one access group called jira-users.

Visit: Admin > User management > Groups

Global Level

The next level is global. This is where a user gets application-wide abilities to administer Jira, make bulk changes, and share objects like filters, dashboards, and subscriptions.

Visit: Admin > System > Global permissions

Project Level

Project permissions are controlled in two places: in a permission scheme and an individual project’s settings. All permission schemes can be accessed from the “issues” admin page. Project-level permissions are in a project’s left sidebar, but the name of the link differs depending on the deployment type and type of project. If a user doesn’t have project-level access they will not be able to see that the project exists, nor will they see individual issues in the project.

Visit: Admin > Issues > Permission schemes
Visit: Project > Project settings > Users and roles (Server & Data Center)
Visit: Project > Project settings > People (Cloud, Company-managed projects)
Visit: Project > Project settings > Access (Cloud, Team-managed projects)

Issue, Workflow, and App-specific Level

Next, there are issue permissions, workflow permissions, and permissions that are specific to installed third-party apps. Use an issue security scheme to limit access to only some issues in a Jira project. Use a workflow condition or validator to limit who can transition an issue. Use the specific settings in third-party apps to grant or limit capabilities as desired.

Visit: Admin > Issues > Issue security schemes
Visit: Admin > Issues > Workflows
Visit: Admin > Apps

Also: User Objects

Additionally, user objects like boards, dashboards, and filters also have their own permission settings. A user might have access to specific projects and issues, but not to all the boards that display them. (Or vice-versa.)

---

Back to intro and image list

[Yuliia_Borivets__SaaSJet_]

I'm in love with the Jira Image of the Day series ❤️ What a brilliant idea!