Problem:
You've restricted read access to a repository by using a content selector that matches a particular path in the repository such as "path =~ /org /com/mycompany/team-a/.*". This works, but now users with this privilege can't see anything under the repository browse UI.
Solution:
This is happening because the folders "/", "/com/", etc. do not match the path expressions.
To fix this you also need to grant browse access to the paths in the tree above the path where they have full access. To do that you can use a regular expression like this one in a content selector:
path =~ "/|/com/|/com/mycompany/|/com/mycompany/team-a/.*"
And set that content selector in a repository content selector privilege with "browse" action. This will allow your users to see the contents of the folders above the path.
Alternatively, you can grant access to all directory listings regardless of where they are in the hierarchy using this content selector:
path =~ ".*/"
Again, assign this to a repository content selector privilege with "browse" action. This will grant access to all directory listings, but will not grant any access to artifacts within a directory.