> ## Documentation Index
> Fetch the complete documentation index at: https://docs.devperform.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Importing Your Team

> Seed your engineer roster from your org / group / workspace in one click.

Rather than adding engineers one by one, an admin can import your entire team — every member of your connected GitHub org, GitLab group, or Bitbucket workspace — to seed the roster.

## How to import

1. Go to **Admin → Engineer Roster**.
2. Click **Import your team**.
3. DevPerform reads your members and creates an engineer for each, with their handle (and name + avatar) attached. **Emails** are filled in automatically from commit metadata — the reliable source across every host and on private repos, since the member APIs rarely expose email.

Imported engineers start **ungrouped** — they appear under an **Unassigned** view until you assign them to [teams](/concepts/teams). DevPerform deliberately does *not* invent a placeholder "Engineering" team for you; the Unassigned view is just a prompt to organize people into the real teams you want.

The import is **idempotent** and case-insensitive on handles, so running it again won't create duplicates — it only adds members who aren't already on the roster. Run it again after your team grows to pull in new hires.

## Requirements

* You must be an **admin**.
* At least one repo must be configured, so DevPerform knows which org / group / workspace to read.
* DevPerform needs **member-read access**: the GitHub App (or OAuth) for GitHub, and the stored OAuth token for GitLab/Bitbucket. If the import returns a permissions error, re-authorize the connection or contact us.

## After importing

Imported engineers behave exactly like manually-added ones: assign them to teams, add additional [handles](/concepts/engineers) if they use multiple accounts, and they'll start showing up in metrics as their PR/MR activity syncs.