Reputation: 11570
I am unable to configure TFS so that the developers on my team can access and clone a repo onto their local machines.
They all receive the following message:
You don't have the authority to view the permissions for this object
I have added them as members of the project. I have even reluctantly made them admins. However, all attempts to resolve this issue have failed.
Upvotes: 24
Views: 30937
Reputation: 3404
In my case, team members role was stakeholder. It should be BASIC to see all repos.
Upvotes: 13
Reputation: 544
if you use azure devops server, you can change access from "Stakeholder" to "Basic",
Upvotes: 1
Reputation: 739
If you are a "StakeHolder" in azure then, you have No access to Repos in Private Projects.
For my project, We had to purchase a Visual Studio Subscription before the repo setting became available.
Microsoft Devops - About access levels - Stakeholder access
Public versus private feature access: Stakeholder access grants access to features differently depending on whether you're working from a private or a public project. To learn more about public projects, see What is a public project.
Visual Studio subscription access: Visual Studio subscribers are entitled to Visual Studio subscription features as a subscriber benefit. When you add those users, be sure to assign them the Visual Studio subscription access level.
The system automatically recognizes their subscription and enables any other features that are included, based on their subscription level.
Upvotes: 3
Reputation: 501
I followed what Ash suggested above and was able dig around and eventually resolve it for my case. Adding some steps here hopefully to help more people find the right page.
To change access from "Stakeholder" to "Basic":
Upvotes: 50
Reputation: 51143
Double check your team members permission of the corresponding repo. Web Portal-Settings-Version Control
Make sure the Contribute permission is allow.
Also check the permission of groups they are in, cause in TFS deny trumps allow.
If a user belongs to two groups, and one of them has a specific permission set to deny, that user will not be able to perform tasks that require that permission even if they belong to a group that has that permission set to allow.
Upvotes: 1
Reputation: 1222
Open admin for the team project.
navigate to security tab.
in the box to add users account you should be able to see the effective permissions on the right side.
User should have Allowed in the "View project level information"
Mouse hover should display "Why" if you click that you should be able to see the source of denied permission.
This is relevant to visual studio 2012 i am using btw.
Upvotes: 3