In our previous blog posts we have described the Confluence Server level access and Space access and will focus on page level restrictions in this blog post. You can get lots of benefits while knowing a few simple tricks about page restrictions.
What are page restrictions and why should I use it?
According to Atlassian, page restrictions allow you to control who can view and/or edit individual pages in a space. For example, if you’re working on a page that shouldn’t be viewed by just anybody, it’s easy to lock it down to the people who need to use it. You can add restrictions for individuals or for Confluence groups.
If you wonder why you should use page level restrictions, then it varies from one use case to another. For example, you can let some of the content in your space be edited by one user while another part of the content is just read-only for him. You can even have “published and approved Quality Management System documents” in the same space with “drafts of new templates/SOP-s”. While the drafts are visible only to the people who are working on those documents and “Approved QMS” can be viewed by anyone, then they can be Edited only by a limited set of “approvers”. If you keep all QMS related content in one Space, then the entire information architecture inside Confluence will be much cleaner and easy to understand.
To read on, please visit our blog post on how to set page restrictions in Confluence
