nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Creating a new Global Permission

Charlie Smith_nosgqk

Is there any way to create a new global permission?

We need some users to have some admin access, however, we'd like to restrict some of the access for these users but not just for a specific project, across the whole instance.

If anyone has any ideas, please let me know.

Accepted answers

Moses Thomas_08kyb0

@Charlie SmithI believe that the JIRA admin group is already created by default, if you need Jira system admin , then create new group and add users to this group

Please see KBA article here

Best!

All comments

Moses Thomas_08kyb0

@Charlie SmithI believe that the JIRA admin group is already created by default, if you need Jira system admin , then create new group and add users to this group

Please see KBA article here

Best!

Charlie Smith_nosgqk

Thank you Moses, however, I'm looking to create a custom permission scheme where I can define what type of access the user has. We want them to be able to edit fields, workflows and issue types but not be able to have access to user management, jira add-ons etc.

Moses Thomas_08kyb0

@Charlie SmithWell Jira is designed in this way,

Types of permissions

There are three types of permissions in Jira applications, and they range from the high-level to granular:

Global permissions - These apply to applications as a whole, not individual projects (for example, whether users can see the other users in the application).
Project permissions - Organized into permission schemes, these apply to projects (e.g. who can see the project's issues, create, edit and assign them). While project admins can assign users to a project, they can't customize the permission schemes for a project. There are lots of project-level permissions you can set to control what users can do within a project.
Issue security permissions - Organized into security schemes, these allow the visibility of individual issues to be adjusted (within the bounds of the project's permissions). For example, issue security permissions can let you set up types of issues that can only be seen by project admins or users in specific groups.

So you need to choose one of these, and in my guest it should be the second, and you said not just a specific project. but a good practice will be to create permission scheme for each project across the whole instance and you can achieve this, may also give them project admin, which is able to set up the permission scheme.

Best!

Charlie Smith_nosgqk

Thank you very much, looks like i have to go down the project permission route.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira

jira-server

permission

administration