We are looking at using a single Confluence server to be an internal and external site. We would split it up by spaces and permissions. Our goal is to have a single tool do both but limit access.
Is this possible and should we do it?
I have seen questions on linking and syncing between internal and external confluence servers but not sharing?
Just curios what others have done and any reason not to do it?
The most simple solution - have one Confluence, exposed internal and externally, and then handle it all by space permissions. Identify your internal users by adding them to a group and then make sure that your internal spaces can only be used by that group, and not by "everyone who can log in" or "anonymous"
You also need to educate your internal users about this very thoroughly so that they know where they are posting/adding content (i.e. internally vs. externally).
Linking also can become challenging as you may create dead links for external users by inadvertently linking to internal pages they cannot access. Same is true for usage of macros like metadata, include etc.
At the very least you should prefix your internal spacesin some way to make them instantly recognizeable. Creating and enforcing different page templates for internal spaces or introducing a page header are another option.
Most of us don’t need much convincing that stakeholder management is important. It just makes sense that keeping everyone in-the-know on projects and assigning clearly defined roles is key to having ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs