Setup Guide

Everything you need to connect your tools to Bilanc.

This guide is for whoever is setting Bilanc up. It lists every integration Bilanc supports, who needs to do it, what access they need, and the exact steps.

You don’t need to connect everything. Connect the version control system you use, plus whichever ticketing, AI, and CI tools your teams rely on. You can always add more later.

How connecting works

Almost everything is done from one screen in the Bilanc dashboard:

1. Sign in to app.bilanc.co as an admin.
2. Go to Admin → Connections.
3. Find the tool you want, click the + (Connect) button on its card, and follow the prompt.

Connections fall into two types:

• OAuth (GitHub, GitLab, Bitbucket, Jira, Slack) — you click Connect and authorize Bilanc in a popup. The person clicking must be signed in to that tool with the right level of access (see each section).
• API key / token (Azure DevOps, Cursor, Codex, Augment, Devin, Incident.io, CircleCI) — you generate a key or token in the other tool first, then paste it into Bilanc when prompted.

Claude Code and GitHub Copilot have a couple of extra options depending on how you run them — see AI Coding Tools.

Once connected, Bilanc backfills roughly the last 2 months of history automatically and then keeps syncing. There’s nothing to schedule.

What you’ll need at a glance

Tool	Connect via	Who needs to do it
GitHub	OAuth + app install	Org owner (to install the GitHub App)
GitLab	OAuth (cloud) or PAT (self-hosted)	Group owner / maintainer
Bitbucket	OAuth	Workspace admin
Azure DevOps	Personal access token (PAT)	Service account with project access
Jira	OAuth	Any user with project access (site admin recommended)
Linear	API key	Workspace admin
Cursor	Admin API key	Cursor team admin
Claude Code (OpenTelemetry, recommended)	Telemetry via settings.json — works with claude.ai, API, Bedrock, Vertex AI	claude.ai org admin, or IT/MDM
Claude Code (Admin API)	Claude Admin API key	Claude org admin/owner
Claude Code (S3)	Daily usage CSV in an S3 bucket	AWS admin
Codex	API key	ChatGPT workspace owner
Augment	API key	Augment admin
Devin	API key	Someone who can create a Devin API key
GitHub Copilot (org)	GitHub OAuth	Org owner
GitHub Copilot (Enterprise)	GitHub OAuth + enterprise slug	Enterprise owner
Posthook	Team install link (CLI on each machine, or MDM)	Bilanc Owner/Manager generates the link; IT or engineers install
Incident.io	API key	Incident.io admin
Slack	OAuth	Anyone who can install Slack apps
CircleCI	Personal API token	Any member (token inherits their access)

A note on permissions

Bilanc only ever requests read access. We pull metadata (pull requests, commits metadata, issues, usage counts, etc.) to compute metrics — we don’t write to your repos, tickets, or channels, and we don’t read source code beyond what’s needed for diff-size metrics.

Deployment & DORA data

Bilanc reports Deployment Frequency, Lead Time for Changes, Change Failure Rate and Time to Restore for every account. Which connections feed them:

• Version control (GitHub, GitLab, Bitbucket, Azure DevOps) – required. Provides pull requests, published releases and Bitbucket deployment records.
• CI/CD (GitHub Actions via GitHub, CircleCI, GitLab CI, Azure Pipelines) – production deploy workflow runs, detected by workflow name, plus failed deployments.
• Incident.io – turns Change Failure Rate and Time to Restore from revert-based proxies into incident-based measurements.

Without CI/CD or incident data the metrics still show, using labelled proxies. See DORA Metrics for exactly how each one is calculated and how to improve it.

Need a hand?

If anything below is unclear or a connection won’t complete, email [e-mail] or reach out on your shared Slack channel and we’ll jump on a call.