It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How do I Setup Default Page Restrictions for Internal and External KB System?

I think the answer is Comala Workflows, but I wanted to clarify.  I am trying to create a primarily internal Knowledge Base site, but have some pages external facing.  Here is what I'm looking to create:

  1. I want the Space to be public (Everyone)
  2. When I create new Pages, I want to restrict that to only Confluence members (Viewing and editing restricted)
  3. If I chose to make a specific Page public, I have no problem manually selecting that on a per page basis

The problem I am running into is that if I set the Space to not allow the public, the Pages inherit that permission and cannot override this setting.  So now every time I create a new page I have to change it from public access to Confluence users only access.

1 answer

0 votes

Hello Michael,

The use case of wanting to use a single space to secure some documents and publically share others is a common use case. The best approach to this, while maybe not the most efficient, is to create one space for internal documents, and another space for publically facing documents. The reason behind this comes down to administrative control and access. If you share a single space for both, you risk accidentally sharing out internal documents publically. Additionally, with a shared space you also risk accidentally hiding your public docs if permissions are adjusted or changed.

Managed two different spaces will be a bit of work at first, but this will allow you to ensure no information is accidentally leaked or hidden. Further information on making a Confluence space available may be found at Make a Space Public.

Additionally, while the Comala Workflows add-on would work, it would only work for Confluence Server or Data Center. That add-on is not available for cloud products.

I hope this proves helpful and provides some guidance for moving forward.

Stephen Sifers

@Stephen Sifers thank you very much for your detailed reply as this helps immensely. 

Like Stephen Sifers likes this

Having two spaces is a horrible solution. The reason to have Confluence is so all of our info can be in one place, not two. 

We have a handful of pages we want to share with clients, but not the rest. We should be able to have permissions on those pages to share. Right now the only way is to go through each page and restrict it manually, then give access to the groups we want. Way too much friction and prone to lots of mistakes. 

We use the cloud solution so Comala is not an option. 

Very disappointed.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in Confluence

Lessons and Learnings: Six Months of Working Remote [Discussion]

Hey there, folks! For most of us, the past six months- yes, you read that right- have been a journey. More people than ever before have pivoted to working remotely, and navigating being on-scre...

4,118 views 4 6
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you