Skip navigation

Permission Patterns Overview

A Permission Pattern is a paradigm for how strict or loose you control who can contribute, what, where and how.

For example:

Business Units - Buckets (Wiki Patterns) Labels: permission_pattern, adoption_pattern
Clean Permissions (Wiki Patterns) Labels: adoption_pattern, permission_pattern
One Wiki space per Group (Wiki Patterns) Labels: adoption_pattern, permission_pattern, navigation_pattern, adoption_antipattern, technical_advice
Permission Granted (Wiki Patterns) Labels: adoption_pattern, permission_pattern

Permission Patterns Overview

  • Clean Permissions - Make it easy to understand
  • One Wiki space per Group - similar to Business Units - Buckets????
  • [Heirarchial Permissions] - overcomplicates situation, makes it difficult for contributors to know where/when they can contribute
  • [Silo Permissions] - frustrating for advanced contributors but safer for new contributors
  • Business Units - Buckets - Silo'd organization but without fine-grained permissions within each business unit, and read-only access accross silos
  • Permission Granted - open by default, anyone can contribute anywhere
  • IdentityMatters - when identity is anonymous, open permissions can be more problematic


Please Log in or sign-up to discuss the pattern.