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.
During the time I've been supporting Jira Service Desk Cloud, one of the most requested functionalities I saw in Cloud is the ability to restrict the customer portal or the creation of tickets to customers with a specific domain, not allowing any other customers with undesired/unknown domains to do it.
In fact, we have some feature requests to implement this option with a considering amount of votes and watchers:
Include Domain Level Restrictions for Service Desk Public Signup
User(s)/Group(s)/Roles security on creating certain "Request Types"
Unfortunately, there are only two options to restrict the customer portal in Jira Service Desk Cloud today:
We understand now that the options above sometimes might not fulfill the needs you've initially planned for your Help desk, even being a deal-breaker to some of our customers.
Since we still don't have a default way to properly restrict the customer portal by domain, this article provides a quick step-by-step to "block" the creation of issues/tickets from users with undesired domains.
Now, you might be asking yourselves: Why did I add "quotes" in the block word? :)
Basically, this workaround consists in:
"Domain of reporter" in ("yourdomain.com", "yourdomain2.com")
Additional to that, I would like to make it clear that these steps only give the option to not consider issues created by undesired domains, however, it will not prevent users from sign-up in your Service desk. It's a temporary workaround while we don't have a supported feature.
Please, feel free to add any thoughts or suggestions you might have in the comments section of the article.
Support Engineer - Atlassian Team
1,115 accepted answers