Allow changing default permissions for logged-in users on a project from Guest to Developer.
Problem to solve
Please allow changing default permissions for logged-in users on a project from Guest to Developer.
When a project is set to Internal or Public, "Any logged in user will have Guest permissions on the repository.". Guest permissions do not allow a user to commit changes to the repository. Some projects are shared across an entire company and it would be useful for everyone to be allowed to commit changes into a non-protected branch. This could be accomplished if there was a setting per-project to decide what permission level logged in users have with the option to give all logged in users Developer permission.
Anyone could use this feature, though it is primarily for Delaney and Sasha.
- Rachel (Release Manager)
- Parker (Product Manager)
- Delaney (Development Team Lead)
- Sasha (Software Developer)
- Presley (Product Designer)
- Devon (DevOps Engineer)
- Sidney (Systems Administrator)
- Sam (Security Analyst)
- Dana (Data Analyst)
Example scenario: I have a documentation repository where various developers across the company write documentation. In order to make sure everyone is empowered to write documentation here, I want there to be a very low barrier-to-entry. If someone wants to write documentation, they may encounter frustration as they realize they are not allowed to commit changes to the repository. If they are making these changes in the Web IDE, it won't even tell them why their commit is failing. If they figure out that they need to request access, they can do so, but then they have to wait for someone to approve that request.
This scenario presents a very messy process that would likely keep the person from writing documentation and is very counter-productive. This also requires there to be someone on the other end to approve the request. What if that person is on vacation? What if there is no clear team that owns that repository?
This is a common issue that several teams have struggled with when managing broadly shared repositories.
Add a setting in the Project General settings to set default permission for logged-in users. This could be a dropdown with "Guest", "Reporter", "Developer", and "Maintainer" as options.
Permissions and Security
Availability & Testing
What does success look like, and how can we measure that?
Success looks like a the ability for a user to contribute to a repository without any extra effort (no requesting access, no manually added users or groups).