-
If you have a user or group and add an authorized project to them then all child projects will also be authorized. That is why I usually group projects below a common parent project (with code management disabled) and then only authorize that parent project, e.g.
company-name |-- dev |-- apps |-- app1 |-- libs |--lib1 |-- sales |-- marketing-campaignsIf you authorize
company-namethe user/group has access to everything. If you only authorizeappsthen everything belowappsis accessible. -
As suggested by @jbauer, this is the only way to get new projects being authorized.
-
Previous Value Current Value Open
Closed
| Type |
New Feature
|
| Priority |
Normal
|
| Assignee | |
| Labels |
No labels
|
Issue Votes (0)
As of now, we created a user with read-only permissions just for cicd, to achieve the goal, we should authorize all parent projects to it's group with the role "Code Reader", if there is a new project, we need to manually authorize the project to the group. Can we create a group that will authorize all projects including new projects in the future?