--- title: "Linear integration for design controls | Qualio" canonical: "https://www.qualio.com/integrations/linear" updatedDate: "2026-11-04T02:17:30.000Z" description: Design controls and quality events from the Linear teams you already run. Qualio reads issues every hour and writes nothing back to Linear. --- # Linear integration for design controls | Qualio Design controls and quality events from the Linear teams you already run. Qualio reads issues every hour and writes nothing back to Linear. ## Design controls built from the Linear teams you already run Qualio reads the issues, parents and relations of the Linear team you choose, as they are, and writes nothing back to Linear. ## What Qualio reads from Linear Qualio reads the issues in the Linear team you choose: title, description, identifier, state, priority, assignee, labels, parent, team, relations, URL, and created and updated dates. You filter on any of them and map them to Qualio fields. Each element keeps its Linear identifier and a link back to Linear. ## Connect Linear in three steps - Create a Linear API key, ideally from a service user, with access to the teams Qualio should read. - Paste it into Qualio under Settings > Integrations & Imports. - Pick the team, where its issues land in Qualio, and your filters and field mappings. Save, and Qualio reads at once, then every hour. ## What you get #### Linear issues become design controls Sync issues to user needs, design inputs and design outputs. Qualio links each test to its requirement and each risk to the element it controls. Before the review, an amber mark shows any requirement with no test. #### Your engineers stay in Linear, and the design controls keep up Each change to an issue reaches its element on the next read. The element carries Qualio's own control status, and shows the Linear state beside it only if you map it as a field. #### Approve the design review and the documentation generates itself Approvers sign electronically. On approval Qualio generates the trace matrix, risk file, specifications and test plans, then exports them with test evidence and change history. #### A bug or support issue becomes a quality event Point a connection at a Linear team with a filter on label, state or priority. Qualio raises each matching issue as an event, such as a complaint or CAPA, with the issue linked. Engineering keeps the issue and quality gets the event. #### Issues you can reference across Qualio Send issues to a Resource Library category, so documents, events and design controls can point to them. ## Where it stops Comments and attachments stay in Linear. Qualio reads the issue and its fields and writes nothing to Linear. #### Use a service user for the key Linear attributes everything an API key does to the person who created it. A key from a service user keeps the connection running when someone leaves, and limits Qualio to the teams that user can see. #### If the key is revoked If the key is revoked, Qualio marks the connection Disconnected at once and pauses reads, with a banner on the Integrations page until an admin reconnects. #### Delete an issue Delete an issue and its element is marked deleted within about six hours; removing it from the design controls is an approval in Qualio. ## Guides ## Questions about the Linear integration ### Does our Linear workspace have to change? No. You pick the team and the filters, then map Linear fields to Qualio fields. Your workflows, states and labels stay as they are. ### Which Qualio records can Linear issues become? Design controls (user needs, design inputs and design outputs), events such as complaints and CAPAs, or items in a Resource Library category. Each connection reads one team into one destination, and you can add more connections. ### How often does Qualio read Linear? The first read runs when you save the connection. After that Qualio reads the team every hour and picks up the issues that changed since the last read. A change to your filters applies on the next read: Qualio marks an issue that stops matching as deleted and brings in one that starts. There is nothing to schedule on your side. ### What access does it need, and what does it write back? A Linear API key with access to the teams Qualio should read, and a Qualio admin to connect it. Qualio uses the key to read and writes nothing with it. Revoke the key in Linear and the connection stops, with nothing to uninstall on the Linear side. ### Who needs a seat? People who write or approve in Qualio pay: the product manager who signs a design review, the person who owns the procedures. An engineer who writes requirements and tests in Linear needs no seat, because Qualio reads them in and nobody edits them there. Everyone who reads or trains is free. ## What a Linear team becomes in Qualio See Linear issues read into Qualio on the demo: issues as design controls and events, with nothing changed in Linear.