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

# Quickstart

> Go from zero to a live dashboard in about 10 minutes.

<Steps>
  <Step title="Sign in">
    Go to [devperform.io](https://devperform.io) and click **Sign in with GitHub**, **GitLab**, or **Bitbucket** — whichever your team uses — and authorize DevPerform. Then connect your repos: GitHub grants org access (see [GitHub Org Setup](/github-org-setup)); GitLab and Bitbucket connect via a button (see [GitLab Setup](/gitlab-setup) and [Bitbucket Setup](/bitbucket-setup)), which auto-tracks your accessible repos.
  </Step>

  <Step title="You're the admin — automatically">
    Whoever connects the code host becomes the account's admin and owner — there's no separate step. Installing the GitHub App or connecting GitLab/Bitbucket grants the admin role on the spot (those flows already require admin rights on the code host side). To bring in teammates, send invites from **Admin → People & Teams** and pick the **Member** or **Admin** role for each invite.
  </Step>

  <Step title="Add repos">
    Connecting GitLab/Bitbucket auto-tracks your repos; for GitHub (or to add more), in **Admin** add them as `owner/repo` (GitHub org/repo, GitLab `group/project`, or Bitbucket `workspace/repo`, e.g. `acme/backend`). All tracked repos are analyzed together. The first sync backfills history in the background.
  </Step>

  <Step title="Build your roster">
    Under **Engineer Roster**, either click **Import your team** to seed your whole org / group / workspace at once ([details](/admin/import-members)), or add engineers manually. Each needs a name and at least one [handle](/concepts/engineers); handles can be multiple per person.
  </Step>

  <Step title="Assign engineers to teams">
    Under **Teams**, create a team hierarchy and assign your engineers. **The analytics dashboards stay locked (shown blurred) until at least one engineer is assigned to a team** — assignment is how DevPerform knows who to count. You're billed only for assigned engineers, and your first 5 are free. The dashboard team filter scopes metrics to a team and its sub-teams.

    ```
    Engineering
    ├── Platform
    └── Product
        ├── Frontend
        └── Backend
    ```
  </Step>

  <Step title="Explore">
    Open **Dashboard** for the team view (last 30 days by default). From there, explore the [Delivery & Quality dashboard](/metrics/dora), [trends and flow](/metrics/flow), and the [executive summary](/dashboard/executive). Use the date picker and team dropdown to scope any view.
  </Step>
</Steps>

## What's next

<CardGroup cols={2}>
  <Card title="Run a survey" icon="clipboard-question" href="/surveys/overview">
    Pair your delivery data with how the team actually feels.
  </Card>

  <Card title="Set team goals" icon="bullseye" href="/goals">
    Commit to measurable working agreements and track them.
  </Card>

  <Card title="Configure DORA" icon="gauge-high" href="/metrics/dora">
    Pick your deploy signal and incident label for accurate DORA.
  </Card>

  <Card title="See your plan" icon="layer-group" href="/plans">
    Find out which metrics your tier unlocks.
  </Card>
</CardGroup>