You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I'm seeking insight or trying to find out if there is a best practice on what is better: having one instance of Confluence to handle both internal only spaces/documents as well as a public-facing Knowledge Base, or having two independent instances of Confluence: one for internal, and one for the public-facing KB.
I'm part of a company that currently has an internal instance of Confluence that we use for internal procedures and information only. We intend to also use Confluence for our new public-facing Knowledge Base. The CTO wants a single instance of Confluence for everything: incorporate the new public-facing KB into our current Confluence install and just govern access via group permissions. However some people within the company believe that a separate Confluence server should be stood up for the public-facing instance.
Our current install of Confluence is only accessible through a specific port #, so if we go with the single instance, this would have to be removed.
Any formal Atlassian insight into this would be much appreciated, as will just insight from anyone else who has thoughts or experience with it. Thank you!