Knowledge Base articles for customers without Confluence access?

[H K]

Hi,

we want to link a KB to our JSD for our customers. Is it possible to link an internal confluence space to the JSD?
--> We need different spaces for different customers and there might be sensitive data that shold not be seen by other customers!

We want our customers to have no account and no access in/to our confluence.
But we want them to be able to read articles of linked spaces embedded in JSD.

Is this possible?

I am a bit confused because of this article "Guide to link Knowledge Base to JIRA Service Desk for unlicensed user" because it sais "Have the same user base in both JSD & Confluence".

Thanks in advance for replies!

[laralg · Accepted solution]

Hello HK, 

I am sorry but you can't. The best solution would be having different Jira SD where each one of them is linked to a different space, if each customer only has access to that SD they would be able to see only the information of that single space linked to that portal.

You do not even need to make Requests for the customer to request in those portal just having them with the confluence page would be enoght.

Regard

[H K]

We will use different SD projects for each customer, so it is possible to add different spaces. But the question is, can we link a space without having customer accounts in our internal confluence?

[laralg]

Are you using cloud or server?

For Server, you will need the customers to be in confluence, but they do not need to consume lincense. Sync them either using Jira as a database (which I recomend as it is more simple) of if you have a AD, but do not put them in confluence-users or confluence-admin.

I recomend this documentation: https://confluence.atlassian.com/jirakb/guide-to-link-knowledge-base-to-jira-service-desk-for-unlicensed-user-816677228.html

(The customers need to be able to reach confluence, if it is in an internal network but Jira isn't it wont work, the customers need to be able to reach it network wise)

[H K]

Okay thank you for your explanation :)