Reputation: 41
After the latest update including the cross-repo policies in the Azure DevOps portal, I can't add project-wide branch protections even though I am the Organization and Project owner.
Is there any special permissions that is required to be assigned to my user?
Thanks, Ví
Solution:
Leave all security groups except "Project Administrators"
Upvotes: 2
Views: 792
Reputation: 3217
I solved the Problem by leaving all groups, except the "Project Administrators" group.
This was based on @ViMans comment.
Quote:
I have realized the problem was related with a user belonging to different groups with different access level. E.g: An organization administrator belonging to the contributor group it will keep the most restrictive access level based in a least privilege philosophy
Upvotes: 1
Reputation: 76700
Is there any special permissions that is required to be assigned to my user?
You should check your user's access level, if they are Stakeholder levels, then they will not have the permissions to add project-wide branch protections.
If set my user as Stakeholder levels on the Organization Settings->Users:
Then, my user will get the states: Yo do not have permission to edict project-wide branch policies:
So, to resolve this issue, you should to assign a higher access level to your users, like Basic.
Hope this helps.
Upvotes: 1