Portal access

[Cassandra Hughes]

Is there a way to customize the portal a bit more in a way that only signed in users can see all projects and non-signed in users can only see and submit requests to one/some project/s. I know this is a stretch but that would have to mean the portal access would need to be open with conditions? 

Ultimately, the problem the is our company implemented new security policies which locked down our Jira portal from external users but we have one project that needs to be open to external requests. We are trying to find a solution to this outside of moving that department out of JSM.

[Harrison Ponce]

Hi @Cassandra Hughes , this is definitely possible!

It's not as easy as one click, however (sorry!) but hopefully it won't be too tedious!

What you can do is set the access (the People section in JSM project settings) for your JSM projects that you want to be only for signed in users. You can do this by adding a group of users to the project at once under the Service Desk Customer role. You should most likely have an all members for directory group in Atlassian Guard (formerly, Atlassian Access) that has all accounts for users that are either synced from an external IdP or added manually/externally. This will give them access to see and submit tickets in the portal when they are logged in. Combine this with setting the Channel access to Restricted in the Portal settings and Customer permissions sections of your JSM project settings.

Then for the project you want available on the portal to external folks (essentially, everyone on the internet), go ahead and set that project(s) portal settings and customer permissions to Open.

It might be nice to test this out in a sandbox if you have a pretty good clone of your production environment and then going to the sandbox portal link in a private/incognito browser to test.

Hope this helps!

[Joseph Chung Yin]

@Cassandra Hughes -

I agreed with what Harrison suggested.  The best way to achieve the visibility of projects listed in the Portal UI is by focusing on each project's Channel access defaulted setup from Open to Restricted.

Once this is done, only authorize users (i.e. customers) can discovery the locked down project(s) in the Portal UI.  

Hope this also helps.

Best, Joseph Chung Yin

[Mariana Silveira Sales]

Hi @Cassandra Hughes 

In addition to @Harrison Ponce configurations suggestions, if you have premium or enterprise license, you can create multiple help centers. 

The Help Center is a central hub that groups all portals in your JSM instance, while the portal is the customer-facing website. 

So you can create and customize help centers individually to cater to your different, distinct audiences.

To create a new help center:

1. Go to Settings () > Products > Jira Service Management > Configuration.
2. In the Help center section, select View all help centers.
3. You’ll be taken to the help center management page. Select Create help center.

After created, access your help center land page and click in Customize -> manage topics and portals. 
Then you can hide the portals you want to.

Here is the documentation: https://support.atlassian.com/jira-service-management-cloud/docs/create-and-manage-help-centers/