Issues & support
Set up Linear
Connect Linear to make your issues searchable — each becomes a document with its description and comment thread, tied to its team, state, assignee and labels, so “what did we decide on ENG-204” answers from the issue itself, archived history included. Read-only.
Before you start
- Linear → Settings → Security & access → Personal API keys → New key. Copy it right away — Linear shows it once. An OAuth app token works too.
- The key reads as the member who created it — it sees exactly the teams that member can see, so a member with access to the right teams is all it takes. Read-only in use; nothing is written to Linear.
- Documents → Linear, paste the API key.
- Only these teams: optional team keys, one per line — the short prefix on a team's issues, the ENG in ENG-204. Blank syncs the whole workspace.
- Choose access groups, Test, then Sync.
What comes in
- Each issue becomes a document titled [ENG-204] title — state, team, assignee, labels and last-updated date, then the description and the comment thread, each comment with who wrote it and when. Completed and cancelled issues come in as history, not just open ones.
- Each team also becomes a concept card.
- Archived issues are included deliberately — Linear auto-archives completed issues after a period each team sets (six months by default) and would otherwise hide them; here that history stays searchable.
Access
A private team's issues follow that team's own active members, re-checked as the source syncs. Public teams' issues keep this source's access groups instead; a private team whose members can't be resolved also falls back to the access groups, so nothing goes invisible. Access stays allow-only either way. Switch How access works to “One list for everything” under Permissions to put everything this source brings in under the chosen access groups instead.
Caps: 5,000 issues per sync, most recently updated first, and 500 comments per issue — Sync notes the issue cap when it bites, and issues already synced stay searchable past it; a longer comment thread is capped and noted per issue. The key reads as whichever member created it, so a key from someone with narrow team access syncs only what that member can see, even with Only these teams left blank. Test connects as the key's member and says whether issues are reachable; it fails with a specific reason when the key is missing or Linear rejects it, and otherwise carries Linear's own message. Revoke access any time by deleting the key under Settings → Security & access → Personal API keys.
Last updated 20 Sep 2026