Problem Definition

Customers might have many application teams, and each team might have many projects.

Currently it is possible to define groups of users and call them 'Team 1', 'Team 2', etc, then grant them access to specific repositories within your projects, or to all repositories within a project by specifying project level permissions.

However, groups can only contain members, not Projects. Theoretically, it's impossible to go from Group to Project, but Bitbucket Server does not provide such reverse navigation. When you click open on a Group you see only members, not its dependencies, like Projects.

Suggested Solution

There should be a concept of teams in Bitbucket Server, which are a higher layer to Project level, so that projects can be grouped into teams. For example:

Team1:
Project1 (Repo1, Repo2)
Project2 (Repo1, Repo2)

Team2:
Project3 (Repo1, Repo2)
Project4 (Repo1, Repo2)