Teams

Teams let you group developers and repositories together so that analytics, code navigation, and insights are focused on the work that actually matters to your group.

What is a team?

A Codity team is not a permission boundary. Creating one does not change who can access your repositories in GitHub, GitLab, or anywhere else. It just tells Codity which repos and developers to pay attention to when that team is selected.

Each team has a name, an optional description, a list of members (matched by login), and a list of repositories.

There is also an optional auto-sync setting that keeps the repo list updated over time as member activity changes. More on that in the creating and managing guide.

What changes when a team is active

Selecting a team from the top navigation scopes the whole dashboard to that team's repos. The Overview metrics, the repo list on the Dashboard page, the Spotlight PR, the Settings and Policy repo lists, and the Code Navigation graph all filter down to what belongs to the team. Each team also saves its own Code Navigation layout independently.

Your selection persists across sessions, so coming back to the dashboard the next day will keep the same team active.

All Repos mode

If no team is selected, or if you pick All repos from the team switcher, the dashboard shows your full set of connected repositories with no filtering. This is the default state when you first sign in.

Teams vs. organizations

An organization is a structure that comes from your version control provider: a GitHub org, a GitLab group, an Azure DevOps organization. Codity picks these up automatically from your authentication and uses them to scope the repository list.

Teams are something you define yourself inside Codity. They are scoped to your connected provider and organization, but let you pick exactly which repositories and developers matter to your group.

Next steps

See Creating and managing teams to get started.