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; } } }

Can you restrict content on JSM + Refined, based on Audience Group?

Manu Viswan

Hi,

So we're using JSM at the moment. We've got one Project, and let's say 100 Portal-only customers. These 100 customers belong to 3 different Groups - who happen to be our main Customer Stakeholders. Let's call them A, B and C.

Currently, on the Portal, all customers can see all request forms and documentations. I want to restrict this based on the Audience Group A, B and C - whether that be Organisations in Jira, or something else.

I am trying out Refined, but apparently the only View Permissions it's giving me are - All users, Logged-in users, and Anonymous (non-logged-in) users. All my customers would be Logged-in users. Basically, when a customer logs into our portal, i want Refined or JSM to check which Audience Group (A, B or C) they belong to, and only show the Request Forms and Knowledge Base Articles that's applicable to them, and hide the rest. Not just hide, but make not accessible. Even if the customer has the URL of another audience's KB article or request form, they shouldn't be able to access it. But apparently Refined doesn't restrict based on Organisation as i can tell.

Is there a way to achieve this? I thought I checked the forums, their documentations, and youtube tutorials - Have i missed something here?

Can someone help please? Greatly appreciated.

Thanks,
Manu

Accepted answers

Benjamin_tmh9yg

Hi @Manu Viswan ,

This may serve your purpose out of the box. You can which request types users can see. After setting the permissions, those who has access to specific forms will see specific KB articles related to that request types.

https://support.atlassian.com/jira-service-management-cloud/docs/add-or-remove-restrictions-on-request-types/

If deciding to further explore Refined, Would suggest submitting them a ticket with the problem you are trying to solve with their app.

https://help.refined.com/?_gl=1%2a5cpnfh%2a_ga%2aMTI3NDU0Mjk0LjE2MTc2NTMxNDM.%2a_ga_2Y6G62J49V%2aMTczODczNDM5NC4xLjEuMTczODczNDM5Ni41OC4wLjkyOTkzMDA2NA..

All comments

Benjamin_tmh9yg

Hi @Manu Viswan ,

https://support.atlassian.com/jira-service-management-cloud/docs/add-or-remove-restrictions-on-request-types/

If deciding to further explore Refined, Would suggest submitting them a ticket with the problem you are trying to solve with their app.

https://help.refined.com/?_gl=1%2a5cpnfh%2a_ga%2aMTI3NDU0Mjk0LjE2MTc2NTMxNDM.%2a_ga_2Y6G62J49V%2aMTczODczNDM5NC4xLjEuMTczODczNDM5Ni41OC4wLjkyOTkzMDA2NA..

Manu Viswan

Hey Benjamin - That's exactly what I wanted, thank you!

I can't seem to restrict Confluence KB articles similarly, since the "Page Restrictions" can only seem to restrict it for Jira users or user-groups, not portal-only customers. Is there a similar setting that allows to restrict KB articles on the portal by customer organisations?

Lotje Euser_nobmhc

hey Manu,

Lotje here from the Refined team. Your use case seems like a good fit for our app. We have helped more organizations like yours to achieve this.

If you'd like to explore our solution about how to "restrict" KB articles, I'd be happy to show you how to achieve that with our Refined app.

Feel free to send me an email or schedule a direct call with me here.

Kind regards,
Lotje

Manu Viswan

Hi Lotje,

Thanks for getting back. Unfortunately, we've decided to not go ahead with Refined because of the issue where when a customer does a self-sign up on the portal, it redirects them to the native Atlassian portal instead of the Refined Portal. This is a deal-breaker for us since we don't want our customers to get confused with the two portals.

Thanks,
Manu.

Adrian Arm

Hi @Manu Viswan

Have you found a solution for your case?

Our case is regarding the KB. We want to grant access only to JSM customers for a space in confluence ie KB.

With Refined for JSM and the JSM KB standard we have the issue like you described:

when a customer does a self-sign up on the portal, it redirects them to the native Atlassian portal instead of the Refined Portal.

Have you found a solution for that?

Welcome!

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

Quick Links

Find more posts tagged with

cloud

refined

jira-service-management-cloud

jira-service-management