This article provides an example of the most common use case for site privacy within MindTouch. While many use cases exist, our customers have achieved the best success with their documentation when setting up a publicly available site which offers both public and private content. This article is most relevant for subject matter experts, content managers, and site owners.
Common use case
The most common use case for page permissions for MindTouch customers is the following:
- Public site
- Public content
- Private content
- Some groups can view
- Some groups can edit
Let's look at an example set up of this scenario below:
- You can set your site to public by unchecking the "Make site private (Anonymous users must sign in)" option within Control Panel > Configuration:
- Viewing the homepage anonymously, we see three categories (Contact Support, Monarch Software, Monarch Technologies):
- When logged in as an admin, I can see an additional category "Product TBD" which is currently set to private:
- The Product TBD page is currently set to private. To expose this to my "Partners" group, and allow members of the "Pro Members" group to be able to edit and create content in this section, I'll set my page restrictions to the following:
- Now let's see what a member of the "Partners" group sees on the homepage:
Note: The "Partners" group cannot edit or create new pages at the homepage level. However, they can see the "Product TBD" category.
- On the "Product TBD" page, a member of the "Partners" group can view, but not edit or create content within this section:
- Because we've set up the permissions accordingly, a member of the "Pro Members" group can see the "Product TBD" category on the homepage, but not edit or create new pages at the homepage level:
- In addition, the "Pro Members" group can now also edit and create content within the "Product TBD" category:
Sample Permission Scenarios
You can also review additional sample permission scenarios within MindTouch.