Disable public access to help center while still allowing email requests from public domains?

[Hope Man]

Hey,

We have 2 instances: 1 with a public-facing help center and 1 that is completely internal-only. We chose this approach cause we honestly did not trust in the maturity of Jira Cloud back then and the documentation was lacking.

All this might have changed, and before trying to figure these things out myself, I wanted to ask the community:

1. Is it possible to disable public access to the help center while still allowing email requests from public domains?

2. I know that one can have multiple Help Centers on the same instance now, but is it possible to configure 1 to be publicly accessible while keeping the other internal (managed domain) only?

We want to make 100% sure that nobody can access our internal help center.

Thank you in advance.

[Tomislav Tobijas · Accepted solution]

Hi @Hope Man ,

1. I'm guessing you'd like for users to be able to create new accounts themselves. Meaning, if someone who is not already registered as a customer sends an email to specific email address associated with the request type, you'd like for ticket to be raised and their account created. If so, you won't be able to get that working unless you have open portal set.
2. Regarding this - I've never tried it personally but I'm guessing it's not possible. There are several open suggestions on the topic which you might want to take a look at > project=JSDCLOUD AND type=Suggestion AND statusCategory!=Done and text ~ "restrict help center"

Cheers,
Tobi

[Hope Man]

Thanks for the great answer.

As mentioned, we always had one instance A with a public-facing help center and another B which can only be accessed by internally managed users.

Do you think it is now feasible to have just one instance with one help center that allows to securely have some JSM project portals exposed to the public while others stay internal-only? I always shied away from this as it seems like a potential nightmare to administer while ensuring security. And what about team-managed Service Desk projects created by our users themselves, will they automatically be exposed to the public etc.

Alternatively, I also considered the idea of creating an Atlassian Automation that syncs issues between instance A and B for Service Desks, so that the public-facing Service Desk from instance B can serve as a funnel for the connected internal project in instance A. But I'm not sure yet how feasible and robust that could be.