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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Online security is not only about the technology and processes, but also about the people. Especially that over 95% of security breaches happen because of human error. And such error may give unauthorized people access to vulnerable data that not only our customers but also our employees entrusted us with. The best example is the recent news about big international corporations having a misconfigured Jira expose their servers. The same may happen also in case of service desks, seeing as nowadays we're in such a hurry to better resolution time that they may become at risk of cyberattack.
We often act as though cyber security and ITSM are completely different areas, with work carried out by different people for different purposes. In fact they both contribute to how we run and manage IT, and they need to work together to provide the protection we need to operate securely in a modern digital age. - Joe the IT Guy.
Just like we should care about our online security, we also should make the best use of the tools that the modern digital age gives us. That's why, in this article, we focus on making Jira Service Desk a safe haven for your customers and employees' data with customer permissions.
It's important to build your protection steadily. Start from the most basic things like defining project roles, organizing users into groups and organizations, specifying their roles within the service desk, creating permission and issue security schemes, and assigning them to each project.
Each user can have a different role within the service desk: administrators, service desk team or customers. And so, the Jira administrators may create and configure projects, customers raise requests, and agents from the service desk team can comment internally (visible only on the issue) or share their comments with customers. Moreover, we can assign more than one role to each user. Remember that the new users (invited via e-mail or who signed up through the Customer Portal) are automatically assigned to Service Desk Customers project role.
If we want to check what project role a user is assigned to, we should:
There's also another way to configure project roles:
Also, we can create additional project roles, i.e. if we need a Service Desk Project Admin. There are only two steps we need to follow:
There are three user groups out of the box:
If we have an internal customer portal, we can classify our users according to their position that grants them a specific authorization level. So, Jira Admins will go to the jira-administrators group because they need all the permissions that are necessary to do their job properly. And a customer support manager or even a team leader of each service desk team will be assigned to i.e. jira-service-desk-project-admins.
To do this:
It's worth to remember, though, that Jira Service Desk also enables us to create Organizations, but we'll discuss it later on.
The first thing to remember after creating user groups is to assign them the right permissions that apply to all projects on our instance. We can grant six permissions:
Global permissions override the Permission schemes. Because of that, we should always grant adequate general permissions to user groups before defining which actions they can perform within a project. And if we can't give some permits to the users, it's probably because they're not assigned to the specific global permission.
To set up overall authorization for the user groups, we should:
We should pay close attention to what project permissions we give to the users, both internal and external, of our Customer Portal. For example, our clients shouldn't have access to every part of the platform, especially to the Jira Administrator menu where they would be able to butcher the most important configurations. That's why Jira Service Desk has various permissions we can grant to the users depending on their role, user group they belong to or other variables.
Permission schemes may differ depending on the needs of the project and what actions specific users need to be able to perform within it. Source: Tempo
As we can see from the graph, there are six groups of permission types that the user can get:
Giving users permissions is quite easy. We just need to:
Remember that we can grant numerous permissions to each user group, project role or other variables available to select.
Project roles are useful for defining specific team members for each project. Referencing project roles (rather than users or groups) in your permissions can help you minimize the number of permission schemes in your system. - Source: Atlassian.
Want to learn more about issue security levels, customer permissions and organizations, and the ways you can extend the native permissions? Read the second part of the article.
Karolina Lasoń [Deviniti]
Atlassian Apps Content Specialist
4 accepted answers