Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

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 to restrict users to specific pages

Restrict external users to spesific pages only in a space.


1 answer

1 accepted

2 votes
Answer accepted
Thomas Bowskill Community Leader Dec 03, 2019



First, I would go about setting up user groups, as in the long-term it makes life easier. Lets say you have a simple case of an Internal and External user group for collaboration...

Then with these groups, you can manage the permissions on the space for each group (this doesn't change what pages they see, but it's useful to review what you give them)

To address your actual question: with the groups you can then start to organise your content in a logical structure that, ideally, limits the number of places you have to restrict access. Reading the Add of Remove Page Restrictions guide is helpful, and the gist of it is:

  • View restrictions will be inherited (if you prevent the external users from seeing a page, they will not be able to see any pages created underneath it)
    • This means that you cannot give them access to a page underneath one they cannot see (this goes back to my earlier point of planning the content tree in advance)
    • If you find this limiting then the Include Page macro may help you aggregate content from different places so there is one view of it (with access restrictions applied)
  • Edit restrictions only apply to the page itself and do not inherit (e.g. if you stop external users from editing a page, it will not stop them editing the child pages)

Hope that helps & good luck


And as a general point unrelated to access RE the page tree structure, I mostly use it now to restrict access and while I pay some effort on building out page trees, I find that it's better to think of Confluence in the same way you do Wikipedia -- how many times do people search content trees in Wikipedia (next to none); focus instead of naming pages in a way that people can search for what they need.

Davin Studer Community Leader Dec 03, 2019

Yes! Groups all the way. This will make you life so much easier going forward. Also, to piggy back on what @Thomas Bowskill said it is important to understand what page restrictions actually do. I see it so many times that person A will add person B to a restricted page and they come to me asking why it is that person B still cannot see the page. Page restriction do not add permissions. Instead, they filter from the pool of people who would normally have access to the page were it to be unrestricted (because they have been given access to the space through space permissions) down to just a certain group of people. So, page restriction do not add permissions. They restrict (take away) permissions.

Like Thomas Bowskill likes this

Suggest an answer

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

What do you think is the most *delightful* Confluence feature? Comment for a prize!

- Create your own custom emoji 🔥 - "Shake for Feedback" on mobile 📱 - An endless supply of GIFs via GIPHY 🤩 Is there anything quite as nice as a pleasant surprise? Comment below with what...

415 views 23 8
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