Skip to content

Redesign GitLab's Permission Allocation Process

Description

Every organization is different with different types of roles and names. Organization restructuring will be inevitable as new innovations and goals come about. The GitLab cannot fulfill everyone's needs by having the permission allocation be static with certain permissions fixed onto a finite number of roles.

Proposal

Each list within a kanban board should define the person and permissions allocated to that list/role.

Permissions should be done in a Kanban style like LeanLabs where a person in an organization would be an item to be placed on a certain list (roles) within the Kanban board. The kanban board should have different swimlane dedicated for permission allocation.

Due to visual scaling, we cannot have a long list of people within the kanban board if the organization is quite large. To fix this, we can abstract away the people and have it be an aggregated count of the number of people within that particular role/list.

What does that fix/improve?

  • Flexibility in permissions allocation and role title
  • An easy change in role in case a person switched jobs or has been promoted
  • Smooth organization restructuring (less tedious than the current design)
  • Less complexity on GitLab's codebase as GitLab Inc. tries to accommodate for everyone's needs

Links / references

http://kanban.leanlabs.io/

/cc @JobV

OSZAR »