grow your wiki
This pattern denotes the "security" scheme used by wikis in which anyone can edit any content. Experience has shown that this can be a powerful tool in conjunction with the Selective Rollback pattern.
Turn off all permissions on the wiki, except those having to do with rollback. Allow any user to perform any action on behalf of the site.
The original http://c2.com
considered this a key aspect of wikis.
Wikipatterns.com is sponsored by Atlassian Software, creators of JIRA, Confluence, Bamboo and Crowd
Designed by Headshift Ltd
I doubt this can be approved when introducing Wiki in an enterprise like a bank. They are usually obsessed with restrictive security, approval flow etc.
I don't think this obsession is fully wrong. Let's say, I read substantial information needed for my decision making from an enterprise Wiki and I'm under time-pressure (always): then there cannot be any risk that someone incompetent has edited the page and I'm using an incorrect information for a decision.
I agree it may be not helpful for the long haul, especially in an environment that relies on authorized information.
However, when introducing a wiki and trying to get it adopted (against the odds of organizational inertia) , just make it clear everything is new and "draft" or "tentative" until the community adopts a mechanism for explicit authorization in the wiki.