Manager Role
Description
In GitLab, Owners are essentially group-level admins. They can do everything. The role directly below owner is master and can't add new people to groups. That slows adoption, as organisations will strive to restrict owner access due to its destructive capabilities.
We can't give master more access, as they are essentially super-developers, the people that can deploy to production. Not necessarily the same people that should have the ability to decide who has access to what.
Proposal
Introduce a manager role. This role can do everything owners can do, minus destructive capabilities.
DOUBT: introducing manager at the project level as an assignable role. This would allow us to reduce permissions of masters (i.e. convert existing masters to manager), so that they can't add people to the project. This would solve some workaround we have.
FOLLOWING THIS: Probably a separate issue, but this would allow us to rename owner to group admin, which reflects the role better.
Overview of available permissions
Group
- owner (group admin)
- manager
- master
- developer
- reporter
- guest
Project
- ? manager
- master
- developer
- reporter
- guest