Question

For some reason our developers can only add projects that they’ve created to Team Explorer, even though they’ve all been given rights to the other projects. I created a top level group and added all of their AD users to it, and I assigned that group rights to access all of our projects.

They can see the projects in Source Control Explorer, and are able to do their work, but if they try to add a project to Team Explorer, the Connect to Team Project dialog box only shows their own projects.

Is there some other set of permissions?

Answer 1

If you want to make everyone can see and operate each others project, you need to put your team group into Project Collection Administrators in Collection level

If you don’t want everyone have admin right,

you need to tell everyone to put the team group into Readers group in the team project they created.

Actually, I don’t think there is a way to create a group in Collection level to access all team projects.

In fact, I think the best solution for you situation should be everyone use the same Team project and put everyone in the Reader group in that team project.

So everyone can create their own project under that team project instead of creating their own team project.

If you still want to let everyone create their own team project,
I suggest you use Team Foundation Server Administration Tool to manage group membership.