Linear Integration - Feature Overview

The Linear integration connects your Linear workspace to 15Five AI. It syncs Linear issues, comments, projects, cycles, initiatives, documents, and user references. Agents use this work context alongside 15Five data when generating insights. The integration installs as a Linear workspace app and is not tied to a specific employee's account.

Access and Availability

Role Requirement
Linear Workspace Admin Required to authorize the connection and, if needed, add the app user to private teams
15Five Company Admin or IT Admin Required to initiate the connection from Agents Hub

The same person can hold both roles, or two people can coordinate setup. The connection installs as a Linear workspace app, so it is not tied to a specific employee's account and keeps working when people change roles or leave.

Note: To ensure the highest level of security, 15Five is continually investing in our overall information security program, resources, and expertise. To review 15Five's security documents, and how we handle your company data, see our Trust Website.

Feature Structure

The integration is configured from Agents Hub > Integrations > Linear.

Permissions and access

A few things to know about how 15Five AI works with your Linear data:

A Linear workspace admin authorizes the connection once. That single connection covers your entire Linear workspace. The connection installs as a workspace app with its own user in Linear, not tied to any individual employee.

Public teams are accessible by default. For private teams, a Linear admin must add the app user to the team before that team's data can sync.

You can disconnect at any time from Agents Hub > Integrations.

What gets synced

Once the integration is connected, 15Five AI syncs issues, comments, projects, and the people associated with them from every team the workspace app can access.

Issues:

  • Title, description, and state
  • Status and priority
  • Team, assignees, creator, parent issues, and sub-issues
  • Labels, cycles, and projects

Comments:

  • Comment body
  • Author

Projects, cycles, and initiatives:

  • Projects and project updates, including status write-ups
  • Cycles — the time-boxed iterations issues are grouped into
  • Initiatives and initiative updates — the higher-level groupings of projects and their status write-ups
  • Documents — the workspace documents your team keeps in Linear

Users (referenced in synced teams):

  • Name, email, and status
  • Account type — whether each user is a person or a connected app/service account

Not synced: Data from private teams the app user has not been added to.

Backfill and Sync Cadence

On first connect, up to one month of history is backfilled. After that, records sync incrementally multiple times per day. Changes to team access are picked up automatically on the next sync cycle — no reconfiguration in 15Five required.

Permissions Requested

When you authorize the connection in Linear, the workspace app is granted:

Permission Purpose
Read Read issues, comments, labels, projects, cycles, initiatives, teams, workflow states, users, documents, and project and initiative updates. This is the core read scope used to sync your work-tracking data.
Write Requested by the Linear connection so the workspace app can access the data required for sync.

Setup

  1. In 15Five, go to Agents Hub, click the Integrations tab, locate Linear, and click Connect.
  2. Sign in to Linear as a workspace admin and authorize the connection.
  3. You'll return to 15Five. 15Five will confirm the integration is live.

Once connected, 15Five AI begins syncing in the background, which typically completes within 24 hours.

Private teams (optional)

Public teams sync automatically once connected. To include a private team:

  1. In Linear, open the private team and add the 15Five AI workspace app user as a member.
  2. On the next sync cycle, that team's issues and related data become available to 15Five AI.

To stop syncing a private team, remove the app user from that team in Linear.

Key Rules

  • The workspace app's team access in Linear is the control point for what 15Five AI can see.
  • Public teams sync automatically. Private teams sync only after a Linear admin adds the app user to that team.
  • Removing the app user from a private team stops that team's data from syncing.
  • Changes are picked up automatically on the next sync cycle — no reconfiguration in 15Five required.
  • The connection is not tied to a specific employee's account, so it keeps working when people change roles or leave.
  • The integration can be disconnected from Agents Hub > Integrations, or by revoking the workspace app from Linear under workspace settings for installed applications.

Common Questions

What Linear data syncs to 15Five AI?

15Five AI syncs issues, comments, projects, cycles, initiatives, documents, and users from Linear teams the workspace app can access. Issue data includes title, description, state, status, priority, team, assignees, creator, parent issues, sub-issues, labels, cycles, and projects. Comment data includes the comment body and author.

What Linear data does not sync to 15Five AI?

Data from private teams the app user has not been added to does not sync. If a private team should be included, a Linear admin must add the app user to that team.

How is Linear access scoped?

Access is scoped through the workspace app's team membership. Public teams are included automatically. Private teams require the app user to be added as a member. Scope is managed in Linear, not in 15Five.

Why does the integration request write permission?

The write permission is requested by the Linear connection so the workspace app can access the data required for sync. 15Five AI does not create, edit, or delete any data in Linear.

Can 15Five AI change Linear data?

No. Although the connection requests a write scope for technical access reasons, 15Five AI only reads data from Linear. It does not create, edit, or delete any issues, comments, projects, or users.

Related Articles

Was this article helpful?

Sorry to hear that. Tell us what was missing →