In the previous recipes, we looked at how to use global permissions to control JIRA access and administrator-level access. In this recipe, we will look at how to control project-level permissions, starting with access to projects.
To control project-level access, we use permission schemes. JIRA comes with a Default Permission Scheme, which is applied automatically to all projects. You can use this scheme and update its permission settings directly. For this recipe, we will start with creating a new permission scheme to illustrate how to create a new scheme from scratch. If you want to just use the default scheme, you can skip the first three steps.
We first need to create a new permission scheme, which can be done with the following steps:
- Navigate to Administration | Issues | Permission Schemes.
- Click on the Add Permission Scheme button.
- Enter the new scheme's name and click on Add.
With the permission scheme created, we then need to grant permissions to users, namely the Browse Projects permission that controls access to projects.
- Click on the Permissions link for the new permission scheme.
- Click on the Add link for the Browse Projects permission.
- Select the permission type to apply; for example, if you want to limit access to only members of a group, you can select the Group option to select the target group and click on Add:
We can grant permissions to multiple users and groups, and once finished, we can apply the permission scheme to the project we want:
Permission schemes define project-level permissions. Unlike global permissions, which can only be granted to groups, these can be granted to specific users, groups, project roles, and more. Once configured, you can apply the scheme to individual projects. This way, different projects can have different permission schemes to suit their needs.