Skip to main content
AI ROI rolls numbers up by team, and ties PRs to people through their code host login. Both are set up in one place: Manage teams. Who can manage teams: organization admins, and roles with the ai-roi:executive or ai-roi:manager permission. See Who sees what.

Open Manage teams

On the AI ROI page, click Manage teams. It is in the Teams setup section of the Engineering Overview, and on the Setup tab’s “Group people into teams” step.

Teams

Create a team and add people

  1. Type a name in New team name, for example “Platform” or “Ingest”, and click Add. Suggested team names are listed too; add them one by one or all at once.
  2. Click Add people and pick the people on the team. The list includes everyone with AI spend or merged PRs in the selected range.
  3. Repeat for each team.
  4. Click Save teams.
Changes show the next time the page loads. Nothing is backfilled or recalculated in the background. If someone else saved teams while you were editing, you are asked to Load their version or Save mine anyway.

Rules

  • One team per person. Adding someone to a team moves them off their old one, so spend and PRs always add up.
  • Everyone on no team is “Unassigned”. “Unassigned” and “No team” are reserved names.
  • Membership applies to the whole date range. Moving someone today moves their past numbers too. Teams have no history.
  • Small teams stay private. Totals for a team with fewer than 5 people using AI are hidden from other developers. The editor tells you before you save.

Suggestions

The editor suggests a team for people it can place, for example when a team’s name appears in the projects or repositories of their PRs, or when someone without merged PRs belongs to a non-engineering group in your Wallets. Suggestions are never applied on their own: accept the ones you agree with.

Before you set up teams

Until at least one team exists, AI ROI uses the groups of your AI seat tracking project’s Wallets, if you have one. Once you create a team here, AI ROI uses only the teams you set up. Wallets are not changed: they keep doing their job for spend limits and approvals.

Renaming or deleting a team

Rename or delete a team in the editor and save. Settings that were tied to the old name are updated in the same save. AI ROI ties a PR to a person through the PR author’s code host login. Most logins are matched automatically, from the email on the person’s commits or their public profile email. Some can’t be matched automatically, usually because the person commits with a personal or no-reply email, or because they use GitLab or Bitbucket. To link one by hand:
  1. In Manage teams, find the person and click Link login.
  2. Pick the login from the list of PR authors nobody is tied to yet, or type it.
  3. The link saves immediately.
  • One login belongs to one person. Linking a login to someone else moves it.
  • One person can have several logins, for example a GitHub login and a GitLab username.
  • GitHub, GitLab and Bitbucket logins are kept apart: a GitLab username never matches a GitHub login of the same name.
  • A manual link wins over any automatic match.
The Setup tab shows how many people with AI spend are matched. Aim for 80% or more.

Audit

Every team save and every login link or unlink is recorded in your organization’s audit log.