Assigning roles

Added
Purpose
Let what a member may do in a shared space be given and understood by a named role, instead of action by action for each member.
Operational principle
If a member is given a role in a space, they can do there what the role allows and nothing else; anyone who knows the role's name knows what the member can do, and giving them a different role changes all of it at once.
State
  • role: Membership -> one Role
  • allows: Role -> set Capability
Actions
  • assignRole Whoever manages the space gives a member a role when they are let in.
  • changeRole Whoever manages the space gives a member a different role, and what the member can do changes with it.
Misfits
  • A set with too many roles, or with custom roles made for each exception, is as hard to read as permissions set person by person.
  • When no role fits a member's part, the manager gives a wider one for convenience, and the member can do more than their part needs.
  • A member cannot tell what their role allows until an action is refused.
Also called
role-based access, access level, permission level
Depends on
Joining
Appears in
Google Docs (owner, editor, commenter, viewer), GitHub repository roles, Notion, Figma

Patterns that act on it

  • Effective access
  • Roles — the shape of the role set: a small stock set, and custom roles made from it
  • Sharing — giving the narrowest role that fits when letting someone in, and raising or removing it later