> ## 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.

# Admin Setup

> Configuring repos, engineers, teams, and org settings from the Admin panel.

The Admin panel is accessible to admins — the user who connected the code host is made an admin (and account owner) automatically, and can grant the role to others by sending an **Admin** invite from **Admin → People & Teams**. It's where you configure everything DevPerform needs to ingest data and display your team.

## Org settings

Under **Admin → Org Settings** you can configure:

* **Organization name** — the display name shown across the app.
* **Burnout threshold** — the open-PR count that triggers the protective 🔥 overload flag in the team table. Default is **5**.
* **Deploy detection mode** — how [DORA](/metrics/dora) detects deploys: **merges** to the default branch (default, zero-config) or real deploys (GitHub Actions workflow runs / GitLab / Bitbucket Deployments). In actions mode, set the workflow or environment name.
* **Incident label** — the issue label DevPerform treats as an incident (GitHub/GitLab labels; Bitbucket matches on title), used for DORA change-failure-rate and time-to-restore.
* **Survey anonymity threshold** — the minimum responses before [survey results](/surveys/results) are revealed. Default is **4**.

## Repos

Add repos as `owner/repo` — GitHub org/repo, GitLab `group/project`, or Bitbucket `workspace/repo` (e.g. `acme/backend`). Connecting GitLab or Bitbucket auto-tracks your accessible repos, so this is mainly for GitHub or extras. All tracked repos are analyzed together for a given date range. Removing a repo only stops DevPerform tracking it — nothing changes on your code host. Adding a repo kicks off an immediate background sync.

## Engineer roster

Add engineers with a name and at least one handle, or **import your whole org / group / workspace at once** — see [Importing your team](/admin/import-members). For surveys, also map each engineer's **work email** (emails are also auto-filled from commit metadata). See [Engineer Roster](/concepts/engineers) for multiple handles and deactivation.

## Teams

Create a nested team hierarchy to enable team filtering. Teams are optional — skip it and all engineers appear together. See [Teams](/concepts/teams).

## Permissions

The admin can add/remove repos, manage engineers and handles, manage teams, and update org settings. Regular (non-admin) users can view dashboards but not the Admin panel.