Shortcut: Ctrl/Cmd + K

Commitlane documentation

Team

Team setup: members, roles, invitations and access to development data.

What this section is for

Create teams and add members so analytics shows the right data. The team selected in the sidebar affects metrics and available repositories. After membership changes, check which data is included in reports.

When to use

  • When first setting up the team in the service.
  • After a reorganisation, when the structure in the tool no longer matches reality.
  • When someone joins or leaves.

Quick start

  1. 1Create teams for the groups whose work and access you want to manage separately.
  2. 2Invite members by email and assign roles deliberately.
  3. 3Check that repositories relevant to each team are enabled in the integration settings.
  4. 4When someone leaves, update membership and access. This does not delete repository commit history.

Key settings

SettingWhat it doesHow to use itCommon mistake
Team name and descriptionShows the team name in the selector and reports.Use a name the team recognises and describe its responsibilities.Names that only make sense to whoever set the tool up.
Member rolesControls what each member can see and change.Grant the narrowest role that lets someone do their job, and revisit it when they change role.Giving everyone the widest role during setup and never coming back to it.

Usage example

Scenario: After a reorganisation, reports still use the previous team membership.

  1. 1Compare the team structure here against how work is actually distributed now.
  2. 2Update membership, then check which repositories each team has enabled.
  3. 3Generate a report with updated membership and check it against repository data. Account for the membership change when comparing older reports.

What this shows: Metrics start describing the current organisation instead of the previous one.

FAQ

Can one person be in several teams?

Yes, and their activity will be counted in each. When you add up team numbers across the organisation, expect overlap.

What happens to metrics when I remove someone?

Historical commits remain in repository data. Membership changes affect which data is selected for the team, so results may differ from previously saved reports.

Tips

  • Check team membership before setting up targets and reports.
  • Update members and roles when people move, and review access periodically.

Related sections