Wiki Patterns
grow your wiki
EditClean Permissions
The Clean Permissions pattern is to set up an authorization system that is easy for wanted users to use and understand, while minimizing the amount of trashing and other forms of revertable grief from the unwanted.
Usage
Post a clear explanation of the permission model prominently on the wiki. For each action requiring authorization, make sure a clear explanation of the authorization criteria is easily accessible.
Example
The original c2.com wiki has a clear and detailed discussion of its Permission Granted scheme and why it works for them.
| Rate this pattern? |
|
Related Patterns
- At the current state of the wiki art, probably the two most common clean permission schemes are Permission Granted and Community Write.
- Registration Required is an anti-pattern, subject to abuse by the bad guys yet a hassle for the good guys.
Further Reading
- The Wiki Way: Quick Collaboration on the Web
Bo Leuf and Ward Cunningham
Adoption Patterns
Adoption Anti-Patterns
Wikipatterns.com is sponsored by Atlassian Software, creators of JIRA, Confluence, Bamboo and Crowd
Designed by Headshift Ltd
I think this is exceptionally good for a public wiki, it keeps up the transparency of the wiki.
However in a corporate environment i think it may be hard to explain that while I could be an administrator of my space/group and have supreme control over that but only be a member of another that isn't allowed to edit pages. But possibily you could have an in house meeting for this anyway which might make it easier to explain.