You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
This is the second part of the article about Jira Service Desk permissions. Read the first part to learn about project roles, user groups, global and project permissions.
Another key point is to define authorization levels for viewing issues. To specify, issues are assigned specific security level which includes a group of users permitted to use them. This way, only those with the right authorizations will be able to access the specific ticket. The variables here enable us to set the access not only for options varying from application access to user and group custom field value to project role and single user. By creating these schemes, we restrict Browse Project permissions in a way. As Browse Project permits users to see all the issues within a service desk, we can limit their visibility by assigning appropriate security levels to them.
Remember that each level may include numerous users, groups or project roles, depending on who needs the specific authorization.
Basically, we can define who may become a customer of our Portal, as well as with whom they can share a request. We can set this up in Project Settings under Customer Permissions.
Also, we can add users to Organizations. Those users invited to Organization and not created in Jira Service Desk won't be added to the jira-service-desk-customer project role. Also, Organizations enable customers to share their requests with other members of their organization. For example, those who are part of the corpoplanet organization will be able to share their requests from a service desk project dedicated to their company with another employee included in it, however, only a specific number of its users will be assigned to a specific project role.
To create Organizations, we need to:
Whenever a new customer joins the service desk, they get restricted access to the Customer Portal. As a part of an organization, these customers aren't added to the Service Desk Customers project role, but they can still raise requests in all projects their organization is assigned to.
To keep ourselves safe from online security threats and boost the usability of Jira Service Desk, we should also make sure that we have some more advanced permissions in place. Just to be sure, we should go more in-depth into the Service Desk accessibility and define the visibility of its other parts to various user groups. In particular to such elements as:
We can limit the visibility of the most important parts of the service desk to the specific user groups, extending the security of the portal
This specific set of advanced permissions is available in Extension for Jira Service Desk app. After installing it, we have to:
If we want to use Visibility feature of the app, we should create additional user groups. Creating two or three user groups per Organization is the most effective way of managing customers because then we'll be able to grant them appropriate permissions, i.e corpoplanet-directors will be able to do more within the service desk than corpoplanet-managers just because they are more inclined to make some decisions. And to make this even easier on us, we can synchronize Organizations with user groups with a feature provided by Extension.
For example, we have a service desk project called Expeditions available for a few user groups, including corpoplanet-directors and corpoplanet-astronauts. Users from corpoplanet-directors will see only request types, such as Introduce an expedition, Register astronauts, Cancel expedition, etc., while those from corpoplanet-astronauts will have access to a different set of request types, i.e. Enter for clearance, Sign up for qualification exams, etc. Both groups also will have some shared request types like Order gear and Order equipment. This way, we ensure that a specific user group can choose from the most relevant requests for them.
Sometimes, simple safety measures as set permissions and limited visibility of some elements for specific user groups is a good start in cybersecurity. But, making sure that our Customer Portal and thus our customer's data is safe and secure is a long-term goal. That's why we shouldn't limit ourselves to the basic service desk protection supported by good anti-malware software. Even adding such things as self-service or automation to our service desk may help secure it. Also, building a process that includes risk and incident management is a necessary precaution against online security threats.
If you’d like to learn more about improving Jira Service Desk, read other articles on the subject available on the Community:
Karolina Lasoń [Deviniti]Marketplace Partner