Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,455,369
Community Members
 
Community Events
175
Community Groups

Jira Service Desk(server), confluence Cloud for Knowledgebase

Greetings all,

We have a fairly robust internal confluence for our company, and an external facing customer service desk.

We are starting our customer knowledge-base phase.

We take e-mail requests from anonymous users, (and create an account) -- I know, not best practice, but what can you do, contracts!

So whatever we end up with has to be completely open, and thus the desire for a second confluence, for example some add-on selections that make using our confluence for a customer facing-knowledge-base not-ideal, such as SAML SSO.

I know that it no longer works the OTHER way:

https://confluence.atlassian.com/servicedeskcloud/blog/2017/12/knowledge-bases-must-be-on-the-same-domain-as-your-service-desk

But has anyone had a similar experience, or maybe some ideas we could try?

1 comment

Hi Calr,

 

From our own experience, we kept on asking customers to create acct for using JSD, as in my opinion  it's great to have some kind of authentication for customers. Creation of anonymous view for Confluence KB and having restrictions based in KB should help in limiting what customers can view. Also recommend revisiting all space to overview page permission configurations as it's most essential part in having anonymous user access to Confluence. 

 

I hope some ideas will help you finding solution.

Like Carl Allen likes this

Hmm The problem is that our service desk HAS to take e-mail requests per contracts.

 

So in order for someone to get an account all they had to do is send an e-mail into our service desk and then they get a customer account, this isn't terrible secure, but its one of our restrictions. 

Comment

Log in or Sign up to comment
TAGS

Atlassian Community Events