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!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

How are security classifications handled in Confluence e.g. Secret, Sensitive, Public?

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?

2 answers

1 accepted

3 votes
Answer accepted

Hello @Kim Read 

Follow this steps to solve this:

  1. Create a page template that includes a mandatory security classification field.
  2. Navigate to the Space Tools of your Confluence space and select Content Tools > Templates.
  3. Click Create new template and select Blank.
  4. Add a new field to the template by clicking on the "+" icon in the toolbar and select "Label".
  5. Enter a label for the field, such as "Security Classification".
  6. Mark the label as "Required" by clicking on the pencil icon and then selecting "Required".
  7. Save the template and give it a name, such as "Secure Document".
  8. When creating a new page, select the "Secure Document" template to ensure that the security classification field is included and required.
  9. Encourage your authors to use the "Secure Document" template for any pages that contain sensitive information.
  10. If necessary, you can also set up restrictions on the space or page level to control who can view and edit the pages with sensitive information.

Isadora,  I think this will work perfectly.  Thank you very much for your insights and suggestion!

Like Isadora_Nichetti likes this

@Kim Read Thank you too! Hope it helps !

0 votes
marc -Collabello--Phase Locked-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Apr 12, 2023

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.

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.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events