goharbor
Customizable default project configuration
Is your feature request related to a problem? Please describe. A user new to the system may not fully understand some of the project configuration settings, or perhaps the server owner wants to enforce specific settings. Currently, if you want to control access to project settings, the only option is to restrict project creation to the admin, which would be an unreasonable burden for a multi-user system.
Describe the solution you'd like Each (or at least, most) project configuration settings should allow for the admin to set the default (eg: projects are private by default), and should also have an admin lock setting (ie: a user cannot modify the setting). If a user wants a locked setting to be modified, they will have to ask an admin to override it. This way an admin can say, for example: -All projects must be private (locked) -projects have vuln scanning enabled by default
Describe the main design/architecture of your solution There would be a copy of the Project Configuration screen under Administration, labeled Project Defaults. Each field would have a lock (Except maybe the CVE one. Not sure what to do with that one.), which is clickable. Here is a slapped together mockup:
Describe the development plan you've considered I am not familiar with the code so I don't know what to add here.
Additional context Add any other context or screenshots about the feature request here.
