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!
Thanks everyone for answering last week’s question. The winner of the random drawing from those who commented is: @LarryBrock I’ll contact you separately with your prize details. This wee...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events