Skip to main content
The engineer roster is the source of truth for who is on your team. DevPerform uses it to connect pull/merge request activity to named engineers.

​
Handles

Each engineer needs at least one username (handle) on your code host — GitHub, GitLab, or Bitbucket. This is how DevPerform matches PR/MR authors and reviewers to people on your roster. Engineers can have multiple handles — useful if someone uses separate personal and work accounts, has handles on more than one host, or changed their username at some point.

​
Adding engineers

Go to Admin → Engineer Roster and click Add Engineer. You’ll need:
  • A display name (how they appear in the dashboard)
  • At least one handle
  • Optionally: email address (for surveys) and team assignment
To seed your whole team at once, use Import your team instead of adding people one by one — see Importing your team. Emails are filled in automatically from commit metadata (the reliable source across hosts and on private repos), and you can always edit one by hand.

​
Deactivating engineers

Clicking the remove button on an engineer deactivates them rather than deleting them. Their historical data remains in the dashboard for past date ranges, but they won’t appear in current views.

​
Engineers not on the roster

If a PR/MR in a tracked repo is authored by someone who isn’t on the roster, that engineer’s data simply won’t appear in the team dashboard. They’re not blocked — their PRs still count for review metrics of engineers who reviewed their work. This is intentional: contractors, external contributors, or bot accounts often author PRs but shouldn’t appear in team metrics.

​
Multiple handles example

An engineer named Alex might have:
  • alex-dev — their work account (used for all PRs in your org)
  • alexsmith — their personal account (used for open-source work that occasionally touches company repos)
Adding both handles ensures both accounts’ activity rolls up to Alex’s row in the dashboard.

​
Arrivals and idle seats

DevPerform re-imports your provider org’s members daily, so new hires appear on the People page automatically (Unassigned — free until you place them on a team). Admins see a banner when new engineers are detected. In the other direction, nobody is ever removed automatically: a team-assigned engineer with no merged activity in 60 days gets an idle flag on the People and Billing pages so you can decide — move them to Unassigned to stop their seat, or keep them. It’s seat hygiene, not a performance signal.