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
Next: Root
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.
In our company we have multiple service management projects. Each of those projects has a generic email address to be used for sending bug reports from any user of our tools. Therefore we want, that any user can send an email, even if they are not yet registered as a customer in our jira instance. In order to achieve that I have to enable the option 'Anyone allowed on the customer access settings' under 'Customer Permissions'.
The problem now is, that these customers can see all portals in our jira instance.
The only way I know to avoid this is to enable the setting 'Customers added to this service project only by agents and admins'. But this setting will disable the possibility to create new issues by email from any not registered user.
Is there any other way?
Hello @Clemens_Raetze
Thank you for your question. It looks like you have the e-mail channel and permissions set-up as you want so I will leave that for now and focus on the portals.
Unfortunately, it seems that you cannot block access to the portal without also blocking access to the e-mail channel. However, you can hide the portals from the home page. This still allows the customer to reach the portal through a direct link, but it adds a little barrier.
If that is something you can work with, go to the portal > Customize > Edit home page layout > and click on the eye of a non-featured portal to have it removed from the home page.
If you need another solution, you might want to look into something like Refined or @K15t GmbH Those products allow you to customize the portal as you see fit, however, you do loose the JSM integration when you use a custom domain and want to link KBA articles directly from an issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Clemens_Raetze ,
As a workaround for your situation, when you can't let users that are not customers yet, you can:
Create a portal via Customer Case app for Jira Cloud from this project, set up forum email to it, and leave this email as a source of communication for not registered customers and then, when they become registered, give them your JSM portal email. So it's like the backup forum for such a situation.
With the app, you also can:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.