Wikis are increasingly being adopted by the enterprise. When people hear the word wiki, Wikipedia often comes to mind. Based on the free platform, Mediawiki, Wikipedia is undoubtedly the world’s most well known wiki. It’s important to note that there are some key differences between a platform such as Mediawiki, and an enterprise wiki like Confluence. One of those key differences is Permissions.

In Mediawiki’s own words:

Because MediaWiki was designed for open-content, it is often not suitable for situations where you want to restrict access to part of the wiki
In the above cases there may be other wiki software (or non-wiki software) which better serves your needs.

Three Levels of Permissions

Confluence meets the needs of the enterprise with its granular three-level permissions structure. This is the first of a three part series which will focus on Global Permissions.

If you have a wiki intranet solution, you may restrict the viewing of some or all parts of your intranet to registered users. Or, if you use a wiki for your public facing documentation or your knowledge base, like Atlassian, you may want to open viewing to anonymous users who are not required to login. Confluence’s Global Permissions lets you do just that.

Check out the short video below for a complete overview of Global Permissions including a live example. You can embed this video in your Confluence pages using the following wiki markup (Requires Confluence 2.10+) – {widget:url=http://app.episodic.com/shows/13/episodes/ppuei42u8b3t}

Next week

Look out for next week’s post which will take a deep look into how Space Permissions in Confluence work.