JSM knowledge base customer access
Asked by Kevin Flachsmann:

I have some trouble setting up access to the knowledge base of my JSM project. Currently I have the following behavior:

**Internal Customer (without Confluence access):**

When an internal customer (with Atlassian account) without Confluence access / licence tries to access the knowledge base directly (<https://DOMAIN.atlassian.net/wiki/spaces/XYZ/>) a error message is shown: No confluence access, try another account. If the user first sings into the servicedesk (<https://DOMAIN.atlassian.net/servicedesk/customer/portals>) he can go to the knowledge base without any issue.

**External Customer (Portal-Only):**

When an external customer (portal-only) tries to access the knowledge base directly, it always gives the error message (No confluence access, try another account), even if a successfull login to the servicedesk was made.

I would expect that the login should work for internal and external customers directly, without previous login to the servicedesk. But even more critical is, that the access for external customers isn't working at all.

Is there any configuration that has to be made to get this fixed?


Answers:
author: Cosmo Denger
body: [@Kevin Flachsmann](/t5/user/viewprofilepage/user-id/5348800) we are struggling with this now as we just launched Confluence as our knowledge base and more importantly as our new employee onboarding experience. Turned out to be a big mistake because we didn't know of the limitations.

We have internal customers that sync through our approved domains. The users can log into JSM first and then that makes direct links to Confluence work. However, this tends to be a showstopper for new employees that just want to access our onboarding materials. We now have to tell them "click on the service desk link and login, then go to the direct Confluence onboarding documentation link". - Cumbersome from a usability standpoint.

We also cannot open our JSM portal or Confluence up to anonymous as there is sensitive information in there meant for the company only.

Simply put, why can't staff use direct links to Confluence without first having to log into JSM (many of which will only ever submit ticket through email ingest)? Is there some automated way we can auto login new users into JSM first without them knowing?  

#frustrated


author: Dan Breyen
body: Hi [@Kevin Flachsmann](/t5/user/viewprofilepage/user-id/5348800) welcome to the community. Here's an article from Atlassian with steps for setting up a KB for JSM. [confluence-jsm](https://www.atlassian.com/software/confluence/resources/guides/extend-functionality/confluence-jsm#link-jsm-confluence)

That's what I did to get it accessible to internal and external customers.

Have you tried setting up a personal email as an external customer for testing? I did that and use it alot for troubleshooting.

Hope that helps.

comments: author: Kevin Flachsmann
body: Thanks for your answer. After long search, I found this article that might describe my issue: <https://confluence.atlassian.com/jirakb/how-jsm-customers-with-an-atlassian-account-can-view-confluence-pages-without-having-a-license-1188780702.html>

It seems that portal only customers only can view knowledge base articles in the customer portal. Directly accessing Confluence is not possible (Workaround anonymous access, guets account, or atlassian account - all options not possible). It's a shame that this is by concept, especially as this setup is possible onprem.


Tags: cloud

jira-service-management

jira-service-management-cloud