How DSALTA integrates with Linear — data collected, setup guide, and automated compliance checks.
Overview
How to connect
Automated checks
Useful links
DSALTA connects to Linear using read-only API access to collect compliance evidence automatically. Data feeds into your Data Library modules.
Read-only access. DSALTA never modifies, creates, or deletes resources in your Linear environment.
DSALTA collects this integration’s data when you connect it — you can refresh it at any time with Sync from integrations on the Integrations page. The compliance checks below re-run once a day at 02:00 America/New_York.
DSALTA reads the Linear user roster — names, emails, roles and active status, which appears on your Access page.It calls these Linear endpoints:
GraphQL POST https://api.linear.app/graphql
GraphQL queries: viewer, users, issues (filtered by your change-request label), issueLabels
Permissions the checks require:readEvery request is a read. DSALTA has no code path that creates, modifies, or deletes anything in your Linear environment.
There is no Reconnect button. Open Integrations → Connected, click Manage on the Linear card, and check the Status tab — it shows either Connected and working properly or Connection issues detected. To restore a broken connection you must Disconnect and connect again, which permanently deletes the data and tests collected from Linear. This usually happens when API tokens expire.
Data is not syncing
Verify the connected account still holds the permissions listed under Before you begin. Then open Integrations in the DSALTA sidebar, stay on the Connected tab, and click Sync from integrations at the top right. That button refreshes every connected integration at once — there is no per-integration sync control.
Create a Linear Personal API key with Read-only permissions to sync users and run change-management compliance tests.Before you begin
Linear account with access to the workspace you want to assess
Permission to create Personal API keys (Settings → Security & access)
If you are a Member rather than an Admin, your workspace admin must have left member API keys enabled (Settings → Administration → API → Member API keys). Admins can always create keys; members cannot when that setting is off.
You will need:
Field
Where to find it
Example
Linear Personal API Key
Settings → Security & access → Personal API keys. Permissions: Read only. · Open
lin_api_…
1
Start in DSALTA
Open Integrations in the DSALTA sidebar, find Linear, and click Connect to open the connect panel. Leave it open — it lists every value you need, and you create those in the steps below.
2
Integrating Linear with DSALTA means
DSALTA will use your API key to read Linear data (users, issues, labels) for security and compliance monitoring.
3
Create a Personal API key
Follow the steps below to create a Personal API key with read-only permissions.In Linear, open Settings → Account → Security & access → Personal API keys and click New API key (direct link: https://linear.app/settings/account/security/api-keys/new). Give it a name such as DSALTA, and for permissions choose Read — DSALTA only ever reads. Leave the team scope unrestricted so the workspace roster and your change-labelled issues are all visible. Copy the key (it begins lin_api_) and paste it into the DSALTA panel.
A personal API key only sees what its owner sees, and can additionally be limited to specific teams. If you create the key from an account that is not in every team — or tick the team restriction — DSALTA’s Access page will be missing users and the change-management checks will evaluate only the issues and labels that key can reach, which can turn a real gap into a passing check. Create the key from an account with workspace-wide visibility.
4
Enter API key
Paste your key below and click Connect.
DSALTA validates the credential when you click Connect. On success the integration moves to the Connected tab, and Manage → Status reads Connected and working properly. Checks begin reporting after the first sync.
If the connection is rejected. Invalid API key or insufficient permissions. Ensure Read is enabled.The on-screen message is generic — see Connection error messages.
Each check below re-runs once a day, at 02:00 America/New_York, while this integration is connected. Click any check for step-by-step remediation guidance.
.png?fit=max&auto=format&n=tsMQJyneJ1xquFUo&q=85&s=4d401cc03b547d99b6f75a6bd170c334)