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
Next: Root
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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I want to ensure that all of our authors utilize a security classification for any and all documents. How is this best achieved in Confluence?
Hello @Kim Read
Follow this steps to solve this:
Isadora, I think this will work perfectly. Thank you very much for your insights and suggestion!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Kim Read
One option is to use separate spaces for the different security classifications. This allows you to control access to these documents on a space level, and also makes it clear to authors that they are creating document e.g. in the "secure" space.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you for the quick reply. And while I like the answer and would work for some organizations, it is a requirement to actually have a security label on the document itself.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.