Skip to main content

Get Started — LinearB Essentials Setup Guide

Set up LinearB Essentials in a clear, phased flow to connect your tools, validate your data, and enable metrics and automation.

Steven Silverstone
Updated by Steven Silverstone

This guide walks you through setting up LinearB Essentials in a clear, phased flow. It focuses on the Essentials experience: Git visibility, AI tooling insights, and gitStream automation, with optional DORA setup for teams that want deployment and incident metrics.

Estimated total time: 20–40 minutes
Who should use this: LinearB Company Admins / Essentials admins
What you’ll need: Admin access to your Git provider (and optionally AI tools, Slack/MS Teams, and API configuration for DORA)

Essentials Setup Progress

Follow the phases below in order. Phases 1–3 cover the core Essentials setup. Phase 4 is optional, and Phase 5 verifies everything is working as expected.

  1. 1. Confirm Git Connection
    Confirm your Git provider is connected, repositories are selected, and data is syncing. (5–10 min)
  2. 2. Configure Users & Access
    Add users, assign roles, and resolve duplicate identities if needed. (5–10 min)
  3. 3. Enable AI Tools & gitStream
    Enable AI Services, configure supported AI tools, and set up gitStream automation. (10–15 min)
  4. 4. Configure DORA Metrics (Optional)
    Configure release detection and incident tracking if you want DORA metrics in Essentials. (Optional: 10–20 min)
  5. 5. Verify Your Setup
    Confirm Git activity, AI insights, automation, and optional DORA metrics are working. (5–10 min)

Essentials Setup Tracker

Use the tracker to check off tasks, assign owners, and coordinate rollout across your team. 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.

Tip: Share the tracker with your platform team and keep it updated as you expand usage across repositories and teams.

What’s Required vs Optional

Category What’s included Why it matters
Required Git connection, repository selection, user access, and verification Without these, Essentials cannot display meaningful Git activity or support adoption.
Recommended AI Services, supported AI tool integrations, and gitStream setup Unlocks the core value of Essentials: AI visibility and automation.
Optional Release detection, Deployment API, Incident API, and DORA metrics Useful for teams that want deployment and incident metrics, but not required for the core Essentials experience.

Before You Begin

  • LinearB: Company Admin privileges
  • Git provider: Admin access or equivalent access to the repositories you want LinearB to follow
  • Optional: Access to GitHub Copilot or Cursor admin settings if you want AI tooling insights
  • Optional: Slack or Microsoft Teams admin access if you want notifications or AI summaries
  • Optional: API access if you plan to configure deployment or incident-based DORA metrics

Essentials Best Practices

Start with Git first
Before enabling AI tools or automation, confirm the correct repositories are connected and Git data is syncing.
  • Keep the first rollout small: start with a focused group of repositories, validate the setup, then expand.
  • Verify repository selection: connecting a Git provider is not enough — make sure the right repositories are selected.
  • Treat DORA as optional: only configure deployment and incident APIs if your team actually needs DORA metrics in Essentials.

Start Here

Begin with Phase 1 — Confirm Git Connection. Once Git data is flowing, continue to user access and then AI tools and gitStream.

Start Phase 1 — Confirm Git Connection →

How did we do?

Contact