Different customers can browse different documents
Asked by KZ:

Hi,

We want to use Jira Service Management with Confluence to allow different customers to see different documents.

We have tried adding customers to groups in Confluence. We set permissions for different documents, allowing different customers to see different documents.

However, because all customers are in the same Confluence instance, they can see each other. From the vendor's perspective, we don't want customers to know about each other.

So we'd like to ask if there's a way to achieve:

1. Different customers can browse different documents
2. Different customers not being able to find each other

Thank you!


Answers:
author: Kris Dewachter
body: Hi [@KZ](/t5/user/viewprofilepage/user-id/5571011) ,

Welcome to the Atlassian Community.

What do you mean with "documents" ? Is that a Confluence Space or a Page ?

How are these customers accessing those "documents"? Via the JSM portal ?

If so, by default there is no way to limit the view of customers on these documents.

What do you mean with "customers are able to find eachother"? Where and how does that occur ?

Best regards,

Kris

comments: author: KZ
body: Hi [@Kris Dewachter](/t5/user/viewprofilepage/user-id/4588367) ,

Thank for response.

Documents mean Confluence Page.

We add customers in Confluence Space and link JSM with Confluence. We set the restrictions on each Confluence page as shown below image.

![page_restriction.png](https://community.atlassian.com/t5/image/serverpage/image-id/342866iC861D853EFC878EB/image-size/large?v=v2&px=999 "page_restriction.png")

If the page I don't allow to access, then I can't find it on JSM portal.

And customers should be added in Confluence, then we can set the restrictions of pages.

Although customers only get URL of JMS Portal, they also can access Confluence via URL.

All customers in the same Space, if they access in Confluence, they can find each other in Teams tab, as below image, also can view members of other teams.

![conf.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/342870i0A235C83FD075494/image-size/large?v=v2&px=999 "conf.jpg")

We only create one organization and one space for JSM and Confluence.

If is there another way to archive that "customers can browse different pages on one JSM instances"?

Or If is there another way to archive that "customers don't find each other of Teams tab on one Confluence instances"?

Best regards,

KZ


author: Kris Dewachter
body: Hi [@KZ](/t5/user/viewprofilepage/user-id/5571011) ,

If your customers have a Confluence license, and have access to Confluence via the backoffice, you can not prevent them from seeing the Teams.

Why do your customers have a Confluence license and backoffice access? Are they also contributing on page content. If customers only need read-access, then they don't need a license and can have access through the JSM portal.

Best regards,

Kris


author: KZ
body: Hi [@Kris Dewachter](/t5/user/viewprofilepage/user-id/4588367) ,

We add customers in Confluence because JSM knowledge base articles can't set the restriction for each articles.

There is a goal that we want customer of **A can read article of X** but **A can't read article of Y** , and customer of **B can't read article of X** but **B can read article of Y** . Both can read **article of Z**.

Is it possible that JSM can achieve this purpose, but I just haven't found the solution yet?

Best regards,

KZ


author: Kris Dewachter
body: Hi [@KZ](/t5/user/viewprofilepage/user-id/5571011) ,

There is currently no way to set customer restrictions to Confluence via the portal.

However, there is a workaround that is described here : <https://confluence.atlassian.com/jirakb/restricting-knowledge-base-articles-to-a-group-of-customers-1224782654.html>

Looking at your setup, I think you already found this article and have it setup accordingly.

Best regards,

Kris


author: KZ
body: Hi [@Kris Dewachter](/t5/user/viewprofilepage/user-id/4588367) ,

Thanks for workaround, this article I didn't find it.

This workaround is very useful, I set the role of customer, and create groups for every company, then set the restriction for Confluence pages to control which groups can access them.

![messageImage_1724406194894.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/343449iD7825F7835C44AFC/image-size/large?v=v2&px=999 "messageImage_1724406194894.jpg")

So it can archive that members in **A group** can read article of X but A group can't read article of Y.

Thank you!

Best regards,

KZ


Tags: cloud

confluence

jira-service-management

jira-service-management-cloud