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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


Best practice: One Confluence site for internal and public data, or two?

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!

1 comment

Davin Studer
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Jul 03, 2018

There is no technical reason why you could not do it all with one instance. You would simply have your public space set to allow anonymous access and set it as the Confluence default space. I think the question you need to answer is are you confident enough with Atlassian's security model and your user's security prowess that you would have them all on the same server. If they are on different servers you definitely hamper a bad actors ability to get at the non-public documentation if they managed to get around Atlassian's security model or manage to phish credentials. As for a public site you might be able to do it on the cheap if you just get a 10 user license.

Like Metehan Ozten likes this

great info, thank you sir.


Log in or Sign up to comment
AUG Leaders

Atlassian Community Events