This is the final post in a three part series about Confluence permissions. In part 1 we focused on Global Permissions and in part 2 we looked at Space Permissions. In this post we’ll take a look at the third level of Confluence permissions, Page Restrictions.

Why do I need permissions?

Security is a major concern for any organisation. Confluence meets the demands of an enterprise environment by keeping your content safe and secure. With a robust permissions structure Confluence is a true enterprise wiki.

Restrict editing of a page

There are times when a wiki page has to be visible by all users, but only editable by a select group. Policies and procedures are a perfect example of this scenario. If you are using Confluence as an intranet, your Human Resources team, or Talent as they are called at Atlassian, can document company policies and procedures in their own space. Using Space Permissions the content in the space can be viewable by all users and using Page Restrictions the editing of specific pages, like policies, can be restricted to only members of the Human Resources team. See the image below for an example.


Restrict viewing of a page

What about the times when you want to make a page invisible to everyone except a certain set of users or groups? Easy. Confluence allows you to restrict the viewing of a page.

If you are a tech writer using Confluence for documentation you may want to restrict the viewing of a page that’s in draft until it’s ready for publishing for public viewing.

See it in action

Check out the short video below to get a complete overview of how Confluence Page Restrictions work. You can embed this video in your Confluence pages using the following wiki markup (Requires Confluence 2.10+) – {widget:url=}

Try it now

Take a guided tour of Confluence and learn how a tech writer uses page restrictions to hide drafts until they are ready for publishing.

Enterprise Wiki Essentials: Confluence Page Restri...