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
Hello to our wonderful Community!
With the majority of us working from home, we are seeing an increase in people using technologies like the Jira Service Desk portal to keep work moving. We thought it might be useful to provide some tips for new (and veteran) Jira Service Desk administrators about how to set portal permissions that are just right for your organization!
Overall, Jira Service Desk has a total of 4 customer permission settings you can set for your portal:
Only people invited by your team to the project can see the portal and create requests 🤫- This is useful for teams who have private use cases that want to ensure only the right people can use their service desk.
Only Jira users can see the portal and create requests 👯♀️- This is a more open version of the previous setting that allows all Jira users (Jira Software/Jira Core/Jira Service Desk) to access the Jira Service Desk portal. This setting is designed for entire organizations using Jira, or if the team(s) raising requests have Jira access. This setting also works for teams using Atlassian Access to sync their user base to Jira.
Anyone can create an account to see the portal and create requests 🔑- This setting means anyone can access your portal; however, they will have to create an account and verify their email before they can have access. This setting is useful for teams who only want verified email accounts creating requests in their Jira Service Desk portal.
Anyone can see the portal and create requests without an account 🌍- This setting opens your portal up to the world so anyone can get help without having to go through a login screen. This is useful for teams providing external customer, vendor, or any sort of third-party support and want to ensure minimum barriers for getting help.
*Agents and project admins can add new customers to a project at any time by including their email address in the “To” or “Cc” field when replying to a request’s email notification. Learn more about users and roles in Jira Service Desk.
In addition to these settings, Jira Service Desk also has built-in CAPTCHA protection to ensure you are protected from spammers and bots. We understand how important security is for Jira Service Desk customers and their stakeholders and are continuing to invest in new functionality to give you even greater control and peace of mind.