nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Restricting Portal Customers

Tom Hopes

In the Site Access section I limited "Who can join your site" by our company domain and tested with a gmail account but was able to join the site.

Wasn't able to see any projects but still I don't want to have to manage this area as a risk for anyone to randomly join.

Am I missing something?

Accepted answers

Petter Gonçalves

Hello Tom,

Welcome to Atlassian community!

The option "Who can join your site" in the site access section of JIRA application is related to the Application licensed access only (JIRA Core, JIRA Software, Agents of JIRA Service Desk) but not to the Customer Portal of JIRA Service Desk.

The customer portal is a completely different view of JIRA dedicated to external folks that can only use JIRA to create and share tickets, not been able to access any internal reports or features of JIRA SD and not been counted as a license in the application billing.

That been said, you have a separate section to define the customers who can sign-up for your site in JIRA Settings > Products > Configuration > Customer permissions:

P.S: The same setting can be accessed in a project level under project settings > Customer permissions.

Unfortunately, the customer portal cannot be restricted by domain, but only for everyone or for the customers you manually add to it. In fact, we have a feature request created to implement the domain restriction in the customer portal:

- Include Domain Level Restrictions for Service Desk Public Signup

Feel free to vote and watch the suggestion to increase its priority and also receive notifications about any updates.

For now, if you want to restrict your portal users by domain, there's a good workaround you can implement:

1 - Use the Domain of the reporter custom field to collect the customer domain in the ticket

2 - Configure an automation rule that will check if the domain of the reporter is the one(s) you expected

3 - If it is a different domain, the automation rule will move the ticket created directly to a "refused" status, where no actions will be taken. Optionally, you can set the automation rule to add a comment with the reason it was refused.

Let me know if this information helps and if you would like to have more details about the workaround provided.

All comments

Petter Gonçalves

Hello Tom,

Welcome to Atlassian community!

That been said, you have a separate section to define the customers who can sign-up for your site in JIRA Settings > Products > Configuration > Customer permissions:

P.S: The same setting can be accessed in a project level under project settings > Customer permissions.

- Include Domain Level Restrictions for Service Desk Public Signup

Feel free to vote and watch the suggestion to increase its priority and also receive notifications about any updates.

For now, if you want to restrict your portal users by domain, there's a good workaround you can implement:

1 - Use the Domain of the reporter custom field to collect the customer domain in the ticket

2 - Configure an automation rule that will check if the domain of the reporter is the one(s) you expected

Let me know if this information helps and if you would like to have more details about the workaround provided.

Tom Hopes

Thanks for your help.

Petter Gonçalves

You are welcome, Tom.

Have a nice weekend.

Skuli Sigurdsson

Hi Petter. In your answer above you say:

"Unfortunately, the customer portal cannot be restricted by domain, but only for everyone or for the customers you manually add to it. In fact, we have a feature request created to implement the domain restriction in the customer portal:"

For manually added customers, how can I restrict them to see/view only one particular portal on customer side?

Jeremy Goldsmith_7d3zbk

This is a good question and unfortunate that it doesn't yet have an answer.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira-software

jira-cloud