Linear
Our Linear integration collects metadata about your workspace’s teams, projects, issues, and cycles, and links that planning work to the pull requests that deliver it. We never read, transmit, or store source code. Sensitive values, such as issue titles, are always encrypted.
Linear connects at the enterprise level, so a single connection covers every team in your Linear workspace.
Connecting Linear
You connect through Linear’s standard OAuth authorization path: a workspace admin consents to the Antenna application, and Linear returns an access token that we store encrypted.
You must be an admin of your Linear workspace to authorize the connection.
Create an Antenna account
Sign up or log in to an Antenna account that belongs to the enterprise you want to connect Linear to.
Open your enterprise Sources page
In Antenna, go to your enterprise Settings, then Sources, to view available integrations.
Start the Linear connection
Click Connect next to Linear and review the summary of what we sync, then click Continue. You are redirected to Linear.
Authorize Antenna
Sign in to Linear as a workspace admin and authorize Antenna to read your workspace. Once authorized, we begin backfilling your historical teams, projects, issues, and users, and we subscribe to Linear webhooks so new activity arrives continuously.
To disconnect, return to Settings > Sources and disconnect Linear. Revoking the grant in Linear also ends our access.
Permissions
We request a single Linear scope.
| Scope | Description |
|---|---|
read | Read workspace, team, project, issue, cycle, label, attachment, and user metadata for planning and delivery metrics. Linear does not offer a narrower read scope, and every alternative ( write, issues:create, admin) adds the ability to modify your workspace. Our token is read-only and cannot create, update, or delete anything in Linear. |
We authorize as an application rather than as the individual who consents, so the connection is not tied to a personal account and does not break when that person leaves or changes roles.
Data Collected
We collect only the metadata required to produce planning and delivery metrics. For the full, provider-independent reference, see Data Collection.
| Area | Data we collect |
|---|---|
| Workspace and teams | Workspace name and ID, team name, ID, and key (the ENG in ENG-123), and team hierarchy |
| Projects | Project name, ID, state and status, lead, target and start dates, progress, and the teams a project spans |
| Issues | Issue ID, identifier and number, title, state and state type, priority, assignee and creator, bot actor, parent issue, project and milestone, due date, and lifecycle timestamps (created, started, completed, canceled, archived, auto-closed) |
| Labels | Label names applied to each issue |
| Cycles | Cycle name, number, owning team, start, end, and completion dates, and the issues in each cycle |
| Users | Linear user ID, name, and email address, used to attribute issues to contributors and match them to their Git activity |
| Attachments | Attachment source type and metadata, which is how we link an issue to the pull requests that implement it |
| Events | Webhook deliveries for issue, project, and cycle changes so metrics stay current |
Issue titles are encrypted at rest. We do not collect issue descriptions or comment bodies.