Embedding Confluence as a knowledge base in a SaaS product

[Nick Gayeski]

What is your experience using confluence as a knowledge base embedded within your SaaS product?  Did you have to make confluence spaces public for them to be accessible? Were you able to limit access to your SaaS users?  How did you do that?  SSO?  What didn't work? 

[Nick Gayeski]

We have not yet, no.

[Priya Keshav]

Did you figure out how to do this within Confluence? We are looking for the same answer.

[Nick Gayeski]

Thanks, Daryl.  I appreciate the feedback and the ideas.  I don't this quite covers it because at the end of the day we don't want a public space.  We want a space only open to users of our platform.  We have integrated our confluence now with our service desk, which makes it available to registered service desk users.  This is closer to what we need.  In any event, thanks!

[Daryl Karan]

Hi Nick, 

What might work best for you with a Knowledge Base requirement, is to create a Draft Space and a Public space. 

The Draft space will act as your internal space where internal users can add knowledge base articles and once the article is approved it can automatically Publish over to the Public Space. The Public space would have view rights only to all users and would be open to anonymous users. 

Confluence is great at collaborating content but not so much with having process and control. This is where you can leverage Atlassian's Marketplace to extend your experience in Confluence Cloud. Comalatech has a solution that can help add process and control to your Knowledge Base articles and once approved it will automatically publish the article to your Public space. 

Comala Document Management and Comala Publishing would be the tools to look at to start adding Content expiry to your Knowledge Base Articles and Publishing the approved content. 

You can try both for free for 30 days from the Atlassian Marketplace. 

Regards, 
Daryl