Phase 3 — Organize Teams & Ownership

In this phase, you will structure your engineering organization inside LinearB. Teams, repositories, and project boards are mapped so dashboards and metrics reflect the real ownership of work.

Goal of this phase: LinearB dashboards reflect the structure of your engineering organization.

How LinearB Organizes Engineering Teams

LinearB organizes engineering activity using three key elements:

• Groups — higher-level organizational units (for example Platform, Infrastructure, or Product Engineering)
• Teams — individual engineering teams
• Ownership mapping — repositories and project boards linked to each team

This structure ensures that delivery metrics and dashboards represent the correct teams.

Step 1 — Create Groups

Groups represent higher-level organizational units that contain multiple teams. They help leadership analyze performance across departments.

Examples

• Platform Engineering
• Product Engineering
• Infrastructure
• Mobile Engineering

How to Create a Group

1. Go to Settings → Teams
2. Click Create Group
3. Enter a group name
4. Save

Step 2 — Create Teams

Teams represent the working units responsible for repositories and projects. Each team will have its own dashboards, metrics, and performance insights.

Examples

• Payments API Team
• Checkout Frontend Team
• Search Infrastructure Team
• Mobile App Team

How to Create a Team

1. Go to Settings → Teams
2. Click Create Team
3. Select the parent group
4. Enter the team name
5. Save

Step 3 — Add Users to Teams

Developers must be assigned to teams so LinearB can correctly attribute commits, pull requests, and metrics.

How to Add Users

1. Go to Settings → Users
2. Select the user
3. Assign them to the appropriate team
4. Save

Step 4 — Merge Duplicate Developer Identities

Developers sometimes appear as multiple users due to different Git email addresses. For example:

• company email
• personal GitHub email
• CI-generated commit email

These identities should be merged so activity is attributed to the correct developer.

How to Merge Identities

1. Go to Settings → Users
2. Locate duplicate identities
3. Select the identities
4. Merge them into the correct user

Step 5 — Map Repositories to Teams

Repositories must be mapped to the teams responsible for maintaining them. This ensures commits and pull requests are attributed to the correct team dashboards.

How to Map Repositories

1. Go to Settings → Git
2. Locate the repository
3. Assign the repository to the responsible team
4. Save

Step 6 — Map Project Boards or Projects

Link project management boards or projects to the teams responsible for delivering that work.

This mapping allows LinearB to connect work items with pull requests.

How to Map Projects

1. Go to Settings → Projects
2. Select the board or project
3. Assign it to the responsible team
4. Save

Verify Phase 3 — Confirm Team Ownership Is Correct

Before moving to Phase 4, confirm that teams and ownership are configured correctly.

Teams

• Each engineering team exists in LinearB
• Teams are assigned to the correct groups

Users

• Developers are assigned to the correct teams
• Duplicate identities are merged

Repositories

• Repositories are mapped to the responsible teams

Project Management

• Boards or projects are mapped to the correct teams

Next Step

With teams and ownership configured, you can now enable advanced features such as AI insights, WorkerB notifications, and gitStream automation.

Continue to Phase 4 — Enable Automation & Insights →