Create multiple service desk projects with different knowledge base (Confluence) access

[Firas Amer]

The use case is - customers are using one service desk project and partners another one, and via the knowledge base (Confluence page) I would like to provide different type of documentation for them.

I would like to make sure that STRICTLY WITHIN THE CUSTOMER SUPPORT PORTAL Customer A added as customer in service desk project A will be able to access ONLY Confluence space A and Partner Customer B added as customer to service desk project B will be able to access Confluence space B (If he could access also confluence space A that would be awesome - but as far as I know only one Confluence space can be added to a service desk project)

Is this possible? Thanks

[Craig Castle-Mead]

Hi @Firas Amer 

The relationship is one confluence space per JSD project, so this should function as you expect. For each JSD project, link to the relevant Confluence space for that project. 

Is this not what you’re seeing?

CCM

[Stefan Post]

I have a similar issue. However the solution des not work. If a confluence space A is linked to one JSD project A and customer from this project A are allowed to read the confluence pages they are allowed to ready any other linked confluence space to any other JSD projects. 

If I link space A to JSD project A and space B to JSD B customer from JSD A (which are no customer in JSD project B) are still able to see space B if they just enter https://XXXXXX.atlassian.net/wiki/.

How can this be avoided without the need to assign a confluence license to every customer?