Groups

Groups help you analyze performance across different parts of your engineering organization — such as remote teams, AI-assisted developers, or offshore contributors. By organizing Git users and repositories into meaningful segments, you can filter your data and set targeted objectives.

Creating and Syncing Groups

Groups can be created manually, or automatically synced from your Git provider.

If you already have teams set up in GitHub (or another connected Git provider), those teams will automatically appear as groups in your workspace. These synced groups are marked with the logo of your Git provider, and any new teams you create in your Git account after connecting will continue to sync automatically.

You can also create custom groups within the app. These are especially useful for capturing non-traditional structures — such as contractors, AI-assisted contributors, or region-based teams — that may not map directly to your Git provider’s team setup.

Managing Groups

You can manage your groups from the Groups tab in Settings. From there, you can select any group to update its members, repositories, child groups, and other settings.

Membership Management

Group members can be managed manually and are also inherited from child groups. If no members have been assigned to a group, all contributors to the group’s repositories will be included by default.

If you remove an inherited member from a parent group, they will also be removed from the child group they originated from.

Members can have multiple membership records — for example, if someone leaves and rejoins a group, or moves between child groups. Setting join and departure dates ensures that each member’s contribution history is accurately attributed to the group.

Repository Management

Repositories can be assigned directly, or inherited from child groups. If no members are assigned, all contributors to the selected repositories are counted toward the group’s metrics.

Group Hierarchies and Inheritance

Groups can now be nested to reflect your team structure. Within the group fly-out, a group can be assigned one or more child groups (in the Groups tab) and a parent group (in the Settings tab). Each child can belong to only one parent, but a parent may have many children.

Parent groups automatically inherit both members and repositories from their child groups. This allows you to roll up activity from multiple sub-teams into a single higher-level view.

You can also assign additional members directly to a parent group without affecting member inheritance.

Assigning repositories to a parent group disables repository inheritance from child groups. This allows you to associate a parent group to repositories of your choosing in cases where child groups contain repositories that may not be representative of the parent group’s work. You can re-enable inheritance by removing all manually assigned repositories.

Alerts and Reports

Groups support custom notifications, including weekly email digests and real-time alerts through Slack or Microsoft Teams. These can be configured independently for each group to help you stay on top of key trends and changes.

Cost Configuration

To track estimated delivery costs, you can assign an average annual cost per contributor to any group. This value is used to calculate metrics like cost per new delivery and can vary by team, region, or role.

Deleting Groups

Groups created manually can be deleted at any time. However, groups that are synced from your Git provider — such as GitHub teams — cannot be removed from within the app.

Deleting a parent group with children will result in the child groups becoming orphaned.