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
Reading through Atlassian training material. I saw s suggestion of having two instances of confluence. This would limit the risk of accidentally publishing internal documents etc to external space.
We will use Confluence for internal knowledge base for different departments.
And then a for JSM help desk.
Maybe some users have feedback if this approach would be overkill and just a External space with restrictions is fine.
For me this would be unnecessary but that is just my situation. It comes down to how many admins you have and if they are adequately trained. Control who can create KB spaces and content in the spaces. Be sure to have a process to control KB pages. Secondarily, consider the true sensitivity of your material.
You don't need two separate Confluence Cloud sites (this is what I refer to as an instance).
You could create two separate Confluence Cloud Spaces:
I see you already have great options here, but I wanted to make you aware of Comala Publishing, which enables space-to-space publishing. You can have an internal draft space and an external facing space, updated only when your content is ready for public consumption. This can also be used for your internal knowledge base.
If you need to have multiple eyes on a document before releasing it into the wild, this is a great option. The intended audience only sees the finalized versions (and no copy & paste required).
I am the PMM for this app, so if you have any questions, I'd love to help!