1. Overview
The Linear integration reads projects, issues, comments, attachments, teams, users, and workflow state through Linear's GraphQL API.
A personal API key or OAuth access token determines the Linear workspace and records visible to Seedling. Seedling verifies the API viewer before storing the connection.
2. Connection and scope
Seedling verifies the provider account before storing the connection. A personal connection remains actor-owned; a workspace connection is administered for the selected Seedling workspace. Credentials are never inferred from an email address or silently promoted between scopes.
- Personal API key
- Created from the Linear member's Security & access settings and bounded by that member's native workspace access.
- OAuth access token
- A customer-managed Linear OAuth application requests the read scope for a workspace connection.
3. Linear data Seedling accesses
Seedling uses synchronized information for source-backed search, operating context, verification, and customer-approved workflows. Availability depends on the connected account, selected resources, provider plan, and native permissions.
- Projects and issues
- Project and issue identity, title, description, status, priority, assignee, creator, team, labels, estimates, dates, and relationships.
- Discussion and files
- Issue comments and attachment metadata or authorized content used as supporting operational evidence.
- Workspace context
- Teams, users, workflow states, cycles, and other visible context needed to interpret delivery records.
4. Read-only permission contract
The connector requires the Linear read scope. Seedling does not create, update, archive, or delete Linear records.
- read — read the workspace information and GraphQL objects visible to the authorized API viewer.
- Personal API keys inherit the key owner's permissions; OAuth grants remain bounded by the authorizing user and workspace.
5. Security and access
- Provider credentials and other connection secrets are encrypted in the workspace tenant data plane, never returned to the browser, and excluded from logs and queue payloads.
- Every source, synchronization, secret lookup, audience contribution, disconnect, and purge remains bound to the exact connection that created it.
- The provider does not expose enough object-level audience evidence for Seedling to reproduce every native permission safely. Workspace content therefore follows the connection's restricted-by-default policy; administrators and stewards receive no raw-content bypass.
- Personal-connection raw content remains visible only to the connecting member in human-facing Seedling surfaces.
- Generated output cannot bypass Seedling's human review, verification, and approval gates.
6. Retention and deletion
- Connected data
- Synchronized Linear records remain while the connection is active and are removed through a durable integration purge after disconnect.
- Credentials
- Stored Linear credentials or connection secrets and connection-owned synchronization state are deleted from active Seedling systems as part of the purge.
- Backups
- Deleted information may remain in encrypted, access-restricted backups until expiry, ordinarily within 35 days after active-system deletion.