Permission schemes, like other schemes, such as notification schemes, are collections of associations between permissions and users or a collection of users. Each permission scheme is a reusable, self-contained entity that can be applied to one or more projects.
Like most schemes, permission schemes are applied on the project level. This allows you to apply fine-grained permissions for each project. Just like project roles, Jira administrators oversee the creation and configuration of permission schemes, and it is up to each project's administrator to choose and decide which permission scheme to use. This way, administrators are encouraged to design their permissions so that they can be reused based on the common needs of their organization. With meaningful scheme names and descriptions, project administrators will be able to choose the scheme that will fit their needs the best instead of requesting a new set of permissions to be set up for each project.
There is, however, some level of freedom for project administrators when it comes to configuration workflows and screens used by their own projects, as we have already seen in earlier chapters covering those two topics. If the permission scheme has the Extended project administration option enabled, then any projects using that permission scheme will allow project administrators to make changes without having to rely on a Jira administrator.
We will first look at how Jira administrators manage and configure permission schemes and then how project administrators can apply them in their projects.
Perform the following steps to start managing permission schemes:
- Browse to the Jira administration console.
- Select the Issues tab and then the Permission schemes option to bring up the Permission schemes page:
On the Permission schemes page, you will see a list of all the permission schemes. From there, you will be able to create new schemes, edit, and delete existing schemes, as well as being able to configure each scheme's permission settings.