Skip to content

Linear

Evidence & policy documents. Read-only ticket state from one Linear team, kept as evidence for your audit.

Status: available now - you connect this yourself

This source is live in the console. Create a read-only personal API key below, connect it on its card in Integrate -> Sources, and your dedicated instance starts collecting. It is an evidence source: connecting it does not create any alerts.

What SheerSight reads

SheerSight reads the tickets of one Linear team that the API key can see. It collects tickets that are open or were updated in the last 90 days; older closed tickets and archived tickets are not collected. For each ticket change it records:

  • the ticket number and title, and its Linear link,
  • its state (for example backlog, started or completed) and priority,
  • the assignee's display name (never their email address) and the ticket's labels,
  • when it was created, updated, completed, canceled or archived.

SheerSight does not keep ticket descriptions. Any text that looks like an email address is replaced with [email], and anything shaped like a key is replaced with [redacted].

It is read-only. SheerSight sends read queries to Linear and nothing else. It never creates, edits, comments on or deletes anything.

What it does not read

  • Other teams. Only the team you name is read.
  • Anything the key cannot see. The key reads what its owner can read in that team.
  • Descriptions and comments.

What you'll need

  • A Linear account that can read the team you want as evidence. Use a dedicated account for continuity, so the key does not stop working when one person leaves.
  • The team key: the short code in front of your ticket numbers, such as SHE in SHE-123.
  • Your dedicated instance enrolled.

Create the read-only credential

  1. In Linear, open Settings -> Account -> Security & access.
  2. Under Personal API keys, create a new key and name it SheerSight evidence.
  3. Give it Read permission only. Never choose Write or Admin.
  4. If Linear lets you limit the key to a team, limit it to the team you want read.
  5. Copy the key straight into the SheerSight console (next section).

Least privilege

A key with Read permission cannot change anything in Linear, even if it were exposed. Keep it to the one team you want as evidence.

Connect it in SheerSight

In the console, open Integrate -> Sources -> Linear and fill in:

Field Value
Linear API key (Read permission) The whole key from step 5, with no spaces.
Team key (optional) The short code in front of your ticket numbers, such as SHE. 1 to 10 letters or digits.

Always enter your team key

When you connect from scratch and leave the team key blank, SheerSight reads the default team, SHE. Unless your team key is SHE, enter yours. When you update credentials, a blank team key keeps the one already saved.

Press Connect. The key is encrypted in your browser before it leaves your screen, so SheerSight staff never see it in clear. Paste it only into the encrypted field, never into chat or a support ticket.

Verify

  1. The relayed credentials entry moves from pending to applied.
  2. The Linear source badge moves from not connected to live.
  3. The card shows no connection error. Collection then runs on your instance.

The ticket data is collected on your dedicated instance. A ticket-by-ticket view in the console is not part of this release. Never copy the key into a terminal or a ticket to test it.

Disconnect and revoke

  • Disconnect the card. In the console, disconnect the Linear card on Integrate -> Sources. The credential is removed from your instance and collection stops.
  • Revoke the key. In Linear, open Settings -> Account -> Security & access, find SheerSight evidence and revoke it. It stops working at once.

For the most complete revocation, do both. See Connecting sources for what the console shows while a disconnect applies.

Data handling and retention

SheerSight stores the ticket fields listed above. For how long that data is kept, where it runs, and what happens when you offboard, see Data handling & retention. The key itself is encrypted in your browser and decrypted only on your dedicated instance. See Security & trust.

Troubleshooting

  • Badge stays not connected, or the card says the key is invalid. Linear refused the key, or it was mistyped, revoked or deleted. Create a new key with Read permission and use Update credentials to send it.
  • The card says the instance has no key. Use Update credentials to send a key with Read permission.
  • The card says the key is not in the right shape. Copy the whole key from Linear again, with no spaces or line breaks, and use Update credentials.
  • The card says the key cannot read the team. The key is valid but has no access to that team. Create a key whose owner can read the team.
  • The card says the team was not found, or the team key is not valid. Check the team key against a ticket number in Linear (the part before the dash), and make sure the key's owner can see that team.
  • Connected but the wrong tickets appear. The team key was left blank and the default team was read. Use Update credentials with your team key.
  • The card says Linear had a temporary problem. No action needed. Polling retries on its own.
  • Something else. See the FAQ, or email security@sheersafe.com for anything security-related.

What SheerSight can and cannot do

The key is read-only, and SheerSight queries only the team you name. SheerSight cannot create, edit, comment on or delete anything in Linear. It only reads.