In Azure DevOps, a default project team will be created when we create a new project in a given collection. We can then add/invite members to this team and assign their level of permission. So far it is clear to me.
However, in my case, I have multiple projects and in each project there shall mostly be static set of developers.
Question:
a) Is it possible to create a default team at collection level (rather than project level) and assign users to it?
b) If srl (a) is possible, how would we instruct Azure DevOps to assign this default team as project team for all projects those shall be created under project collection ?
For example: Within a collection called Services, I have projects with users like below
Service A will have developers x, y
Service B will have developers x, y
Service C will have developers x, y, z
I prefer a default team with users (x, y); and this team will be assigned to all projects those are created under Services collection.
Exception: Service C has an extra developer Z. This is fine since we can visit project and explicitly add this developer.
a) Is it possible to create a default team at collection level (rather than project level) and assign users to it?
No, it's impossible. In Azure DevOps, we provide collection-project-team structure.
Within a project, you can add teams
You could take a look at our official doc here-- About projects and scaling your organization and then decide if you need to create multiple projects or teams in your scenario.
As the above doc mentioned, we would suggest you handle a single project. Can a user account belong to more than one team?
Yes. When you add user accounts to a project, you can add them as members of the project, or you can add them to one or more teams added to the project.
Besides, you are also be able to structure hierarchical teams. Although there's no concept of subteams, you can create teams whose area paths are under another team, which effectively creates a hierarchy of teams. To learn more, see Add another team.