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:
- Sign in to app.bilanc.co as an admin.
- Go to Admin → Connections.
- 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, 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 license 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
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.
Need a hand?
If anything below is unclear or a connection won’t complete, email sam@bilanc.co or reach out on your shared Slack channel and we’ll jump on a call. 
