Learn more about Jira Cloud products, features, plans, and migration.
Integrate Jira Cloud with Confluence, development tools, apps, and self-hosted tools using OAuth and feature flags.
Control who has access to your Jira Cloud products and give them the right permissions to perform their role.
Learn how to set up, customize, and manage Jira Cloud projects.
Explore issues, issue types, issue custom fields, issue screens, custom field context, and issue field configurations in Jira Cloud.
Define the lifecycle of your work and learn about issue workflow schemes and the issue collector.
Learn more on how you can set up Jira Cloud for your team.
When you use a custom permission scheme, if the permission settings are different from those of the standard permission scheme, you will see a permission error similar to the following:
Explanation of permission scheme errors
Jira Service Management considers the differences between your permission scheme and the standard Jira Service Management permission scheme as errors in the following two categories:
Critical errors (red): These errors either cause certain administration functionality to be disabled (for example you cannot add agents to your service project), or impact the day-to-day use of your service project (for example customers cannot log in to the Customer Portal). This table describes what Jira Service Management considers as critical errors. You cannot dismiss these error messages, as you must fix them in order for Jira Service Management to return to normal operation.
Non-critical errors (yellow): Permission scheme differences that do not impact how Jira Service Management works are considered as non-critical errors. You can dismiss these error messages if you do not want to use the standard permission setup.
You can resolve the permission errors by changing the permission scheme yourself or using the Fix permissions button in the error message.
What does the Fix permissions button do?
The Fix permissions button on the message disassociates your custom permission scheme with the service project, creates a copy of your permission scheme with the name of <your_permission_scheme [number]>, and associates this new scheme with the project. The new scheme fixes the errors by:
Granting the standard permissions to the Administrators and Service Desk Team roles, and the Service Desk Customer - Portal Access security type.
Removing the Service Desk Customers role from all the permissions assigned.
Leaving other permission setup as is.
Your original permission scheme
The new permission scheme
The name of the original one is 'Jira Service Management Permission scheme for Project OA'.
The following permissions are set up differently from the standard permission scheme:
After you click Fix permissions, the 'Jira Service Management Permission scheme for Project OA' permission scheme is dissociated with the project, and a new permission scheme called 'Jira Service Management Permission scheme for Project OA 1' will be applied to your service project.
What are critical permission errors?
Critical permission errors cause certain functionality of Jira Service Management to be disabled.
The Administrators role does not have the following required permissions:
The Service Desk Customer - Portal Access security type does not have the following required permissions:
The Service Desk Customers role is granted any permission directly.
Granting permissions to this role gives customers access to Jira functions. Customers should only have access to a Customer Portal and permissions should be granted to the Service Desk Customer - Portal Access security type.
As a result, administrators will not be able to add any customers to the service project. Open service projects will become restricted. Public signup will be disabled.
The Service Desk Team role does not have the following required permissions:
The Service Desk Team role is granted the Administer Projects permission.
Granting the Administer Projects permission to your agents means that all agents become administrators for your service project.
This is a severe security issue. Jira Service Management will disable the functionality of agent management. As a result, administrators will not be able to add any agents.
Was this helpful?