Azure DevOps User Access Levels OverviewIn Azure DevOps, the access and visibility of repositories depends on user access levels.Azure DevOps (ad) Make sure you have at least to the Basic access levelIf user can not see it reduce their number of items in directory andor upgrade them into basic or higher. It needs to be set up this way because, in general, not every user with access to a repo can see and do anything w/ the repository.
User Access Levels
In the context of Azure DevOps, access levels are packages that contain sets of features and capacities. The main levels include:
Stakeholder: Advance access for view, track only work items.
If Basic — Access to repositories, Full access ⇒ Essential features
Premium: More features to help you organize larger projects.
Visual Studio Subscriber, Advanced features for Visual Studio users
Project Collection Administrator or Organization Owner permissions to set access level for a user. They provide you the ability to control user permission in a very efficient way organization wide.
Steps To Upgrade User Access Level
Go to the Azure DevOps navigate on-browser pressing this.
Select Users from the menu.
Locate the user for whom you want to modify this access level.
Find your current access level and click on it then select Basic or higher in the drop down.
Save your changes.
Once this access level is set, the user can see and get to into all of those repositories that they were previously denied from.
Knowing these permissions is important to successfully work together as part of a team in Azure DevOps and ensure that all the team members have required access to what they need.