Skip to main content

Get Started — LinearB Enterprise Setup Guide

Set up LinearB across your organization, configure teams and access, and validate your data to ensure accurate metrics and scalable workflows.

Steven Silverstone
Updated by Steven Silverstone

A phased implementation path for configuring LinearB in an enterprise engineering organization. Complete the phases in order. Each phase ends with a concrete verification checkpoint so you can confirm setup is correct before moving on.

Estimated total time: 45–90 minutes
Who should use this: LinearB Company Admins / Enterprise admins
What you’ll need: Admin access to Git + your project management tool (and optionally Slack or Microsoft Teams)

Enterprise Setup Progress

Use the phases below as your primary setup path. Phases 1–3 are required for reliable core metrics. Phase 4 is optional and adds automation and adoption features. Phase 5 verifies everything end-to-end.

  1. 1. Connect Your Systems
    Connect Git and your project management tool so LinearB can ingest data. (10–25 min)
  2. 2. Configure Data & Metrics Accuracy
    Configure release detection, exclusions, bots, and metric calculations. (15–25 min)
  3. 3. Organize Teams & Ownership
    Create groups, assign users, and map repositories and boards to teams. (20–40 min)
  4. 4. Enable Automation & Insights
    Enable AI services, WorkerB notifications, and gitStream automation. (Optional: 15–45 min)
  5. 5. Verify Your Setup
    Confirm data flow, accuracy settings, team mapping, and dashboards. (5–10 min)

Enterprise Setup Tracker

Use the tracker to check off tasks, assign owners, and coordinate rollout across teams. We recommend making your own Google Sheets copy so you can collaborate and update status live.

Use Create your own copy to track setup collaboratively in Google Sheets, or download an Excel version if your organization prefers offline tracking.

  • Track completion of each setup phase
  • Assign setup tasks to platform owners
  • Capture decisions (exclusions, release detection, team mapping)
  • Share status with stakeholders during rollout

Tip: Share this tracker with your platform team and keep it updated as you onboard additional teams.

What’s Required vs Optional

Category What’s included Why it matters
Required Git integration, PM integration, release detection, exclusions, teams/users, repo & board/project mapping Without these, dashboards and metrics are incomplete or inaccurate.
Recommended Enable LinearB AI Services (org-wide), AI tools usage (if applicable), incident tracking rules (for DORA) Unlocks higher-quality insights and stronger DORA coverage.
Optional WorkerB (Slack/Microsoft Teams), gitStream automation, SSO/SCIM Improves adoption and workflow automation. Not required to start getting value from core dashboards.

Enterprise Best Practices

Use service accounts for integrations
Connect Git and your PM tool using a dedicated service account to prevent outages if an employee leaves or permissions change.
  • Start with a pilot: one group + 2–3 teams, validate accuracy, then expand.
  • Decide ownership early: who owns release detection rules, exclusions, and team mapping.
  • Document your choices: keep a record of regex patterns and your metric calculation strategy.

Before You Begin

  • LinearB: Company Admin privileges
  • Git provider: Admin access (or equivalent permissions) for the org/projects you want to connect
  • Project management tool: Admin access (Jira / Azure Boards / Shortcut)
  • Optional: Slack or Microsoft Teams admin rights (WorkerB)

Tip: Use the Enterprise Setup Tracker above to assign owners and track completion across phases.

Start Here

Begin with Phase 1 — Connect Your Systems. Once data is flowing, continue to Phase 2 to make metrics accurate.

Start Phase 1 — Connect Your Systems →

How did we do?

Contact