Block Users from loggin in but still allow them to create an account.

Joao Zampa

Is there a way to block Users from logging in but still allow them to create an account.

Here is our case and why we want to accomplish the above.

We need to make the help center only available to Employees but we still need to allow external requests that come via email to become tickets.

I know that Jira does not have this feature(IMHO this is a basic feature), so I was thinking that I could use the configuration in Jira (see below ) and try to block the login from users that are not part of our domains.

As I am new on Scriptrunner, I don't know if it would be capable of such a thing.

Can Scriptrunner block specific users from logging in?

 

Jira Configuration 

Can customers create their own accounts?

Yes, by signing up or sending a request

Can customers access and send requests from the help center without logging in?

No

Petter Gonçalves

Hello @Joao Zampa

Thank you for reaching out.

Per your description, I understand you would like to allow your customers to create tickets through e-mail in your help desk, however, they should not be able to access the customer portal, allowing only users from specific domains to do it. Is that correct?

In order to provide you with more context and better understand what are you trying to achieve, can you please provide us with more details on why are you trying to achieve it?

I ask this question because the customer portal is a separate view dedicated only to customers in your Service desk. That being said, you can restrict your Customers from seeing each other tickets and any other settings in that view apart from their own created tickets, so I believe I'm struggling to understand what would be the functional achievement of restricting them from access the portal when they are able to create tickets. Can you clarify this for us?

If you need a clear segmentation of external customers x Employee, I believe you can achieve it by using the "Domain of Reporter" custom field that identifies the domain of the user creating the issue, so you can use it to create separate queues.

We will be waiting for your answer to provide you with further information.