DeliveryCompass
Getting started

Setup guide

Self-serve setup takes about a minute for your account. GitHub import runs in the background after you finish. This guide walks through each step and what to do if something looks wrong.

Before you start

  • Know your GitHub organization login (the slug in github.com/your-org).
  • Have permission to install the DeliveryCompass GitHub App on that org, or create a personal access token with read:org and repo scopes as a fallback.
  • Understand that import is statistics only — PR and review metadata, not source code. See what we import.
  • You can register with email and password or Sign up with GitHub when your primary GitHub email is public.
  • Plan a few minutes after setup to assign repositories to teams — team KPIs stay empty until you map repos.

Setup steps

01
AccountOn Start setup, sign up with email and password or Sign up with GitHub. Optionally enter your GitHub org login to create your workspace.
02
GitHubInstall the DeliveryCompass GitHub App on your organization (recommended). You can skip and connect later from Profile → GitHub. A personal access token is available under Advanced on the same page.
03
FinishConfirm setup complete. The worker imports repositories, teams, and pull request history automatically — usually within minutes for typical orgs.

Typical time to first dashboard: under 10 minutes with GitHub connected and repos mapped.

Alternative: personal access token

Most teams use the DeliveryCompass GitHub App. Use a PAT only if you cannot install the App.

Create a classic or fine-grained personal access token with read access to your organization and repositories:

  • read:org — list teams and organization repositories
  • repo — read pull requests, reviews, and PR metadata (read-only is sufficient)

Paste the token under Advanced on Profile → GitHub. If validation fails, see troubleshooting: GitHub connection invalid.

How long until data appears?

Account creation is immediate. After you finish setup with a valid GitHub App install or PAT, the worker runs a bootstrap import of full PR history — typically minutes for small orgs, longer for large histories.

Organization-level metrics may appear before team cards populate. Team KPIs need both bootstrap progress and repo mapping.

Daily syncs refresh roughly the last 90 days; see sync schedule.

Map repositories to teams

After import completes, open Teams & repos. Drag repositories from the unassigned pool onto team cards. Team KPIs only include mapped repos.

See the Teams & repos guide for mapping rules.

Common situations

For step-by-step fixes (empty dashboard, GitHub connection issues, login problems, stale metrics, and more), see the troubleshooting guide.