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:
But has anyone had a similar experience, or maybe some ideas we could try?
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.