---
updatedAt: 2026-06-15T14:38:14.000Z
agentTools:
  projectIndex: https://docs.socket.dev/llms.txt
---

# Linear Integration

Connect your Linear workspace to Socket to create and manage Linear issues from alerts, with manual creation and automated ticketing rules.

> 📘
>
> The Linear integration is currently in **Beta** and is available on **Business** and **Enterprise** plans.

Connect your Linear workspace to Socket to create and manage Linear issues directly from Socket alerts. Create issues manually from individual alerts, or set up automated ticketing rules that create and update Linear issues based on alert events in your organization.

The integration connects to Linear using OAuth. Authorization happens entirely from the Socket dashboard — there is no separate app to install in a third-party admin console.

### Key capabilities

* **Manual issue creation** — Create a Linear issue from alerts in the Socket dashboard.
* **Automated ticketing rules** — Define rules that automatically create Linear issues when specific alert events occur, with configurable conditions, team, project, priority, and labels.
* **Multi-workspace support** — Connect more than one Linear workspace to a single Socket organization.
* **Multi-organization support** — A single Linear connection can optionally be shared across multiple Socket organizations.

## Prerequisites

* Confirm your Socket account is on a **Business** or **Enterprise** plan.
* Have a Linear workspace ready, with permission to authorize apps for the workspace and teams you want to connect.
* Hold an **Owner** or **Admin** role in your Socket organization (required to connect and disconnect the integration).

## Connect Linear to Socket

### Step 1: Open the Linear integration page

In the Socket dashboard, go to **Settings → Integrations → Linear** for your organization, then click **Connect**.

A dialog opens with step-by-step instructions and an installation link.

<Image src="https://files.readme.io/2df09fae8e597dc6cb4c2ffb0cc63c288cbcc573b5bd7edd31beec7d776782a3-image.png" align="center" width="600px" />

### Step 2: Start the authorization

1. Click **Install** to open the Linear authorization window.
2. If the authorization window does not open, your browser may be blocking popups. Allow popups for this site, or copy the installation link shown in the dialog and open it in a new browser tab.

<Image src="https://files.readme.io/11c2a37092a416b59a81c34c7bbd1d42230f7ae5d58b34763acdfded146cc05a-linear-auth.png" align="center" width="680px" />

### Step 3: Approve the requested permissions in Linear

In the Linear authorization window:

1. Select the correct **workspace** in the top-left corner.
2. Select the **teams** you want Socket to be able to create issues for.
3. Review the requested permissions and click **Authorize**.

Socket requests the following Linear OAuth scopes:

* **Read** — Read workspace data such as teams, projects, labels, and priorities.
* **Write** — Create and update issues on your behalf.
* **Create issues** — Create new issues from alerts and ticketing rules.
* **Create comments** — Add comments to issues to keep them in sync with alert activity.
* **Subscribe to issue updates** — Receive notifications when issues are updated.

### Step 4: Verify the connection

After you authorize, the Socket dashboard reloads automatically and the connection appears under **Settings → Integrations → Linear** with a **Connected** status badge, including who connected it and when.

<Image src="https://files.readme.io/3ac07748a23f3a0a19307d2891d8945414cb17fe43d4339d8ceaaa2a08986ed4-image.png" align="center" width="600px" />

Tip: To connect additional Linear workspaces, repeat the steps above.

## Disconnect Linear

To disconnect a Linear workspace from your Socket organization:

1. Go to **Settings → Integrations → Linear** in the Socket dashboard.
2. Find the Linear connection you want to remove.
3. Click the button with the 3 dots, and select **Disconnect...**, then confirm.

<Image src="https://files.readme.io/7f4a124129ccde24aeb43d7e422c59353e584c11e6be00e71d646242be36d748-image.png" align="center" width="500px" />

This removes the link between the Linear workspace and your Socket organization. If the same connection is shared with another Socket organization, it remains connected to that organization.

Alternatively, a Linear admin can revoke the connection in the Linear workspace settings.

> 📘
>
> If a connection shows an **Error** or **revoked** status, remove the connection and create a new one to restore access.

## Multi-organization support

By default, a Linear connection is tied to the Socket organization that authorized it. A single Linear connection can also be shared across multiple Socket organizations. When you authorize a connection that is eligible to be shared, Socket prompts you to select which organization to connect it to.

1. Go to **Settings → Integrations → Linear** in the Socket dashboard.
2. Find the Linear connection you want to remove.
3. Click the button with the 3 dots, and select **Options...**
4. Toggle the switch to allow shared connection, and click the **Connect...** button.

<Image src="https://files.readme.io/8acda40a212cb9de1b25d85e1f07a3fd6a89ba97cf187736de31f53c9771a453-image.png" align="center" width="600px" />

5. Select the organization you want to connect, and confirm the connection.

## Create Linear issues from alerts

Once the integration is connected, you can create Linear issues directly from alerts in the Socket dashboard.

1. Open an alert in the Socket dashboard.
2. Click the **Create Ticket** button.
3. Select the Linear workspace, team, project, and fill in any additional fields.
4. Submit to create the issue.

The created issue is linked to the alert, and a link to the Linear issue appears on the alert so you can navigate directly to it.

<Image src="https://files.readme.io/dd36dc2698309d744862ac0bd641b006fcd177ab9ec0b57268d2e30da6f6ac65-image.png" align="center" width="600px" />

## Automated ticketing rules

Automated ticketing rules let you define conditions under which Linear issues are automatically created and updated. Configure these rules from **Settings → Integrations → Ticketing** in the Socket dashboard.

> 📘
>
> Ticketing is available on **Business** and **Enterprise** plans.

### Create a ticketing rule

Click **Create Configuration** to start the wizard:

#### 1. Select events

Choose which events should trigger the rule.

<Image src="https://files.readme.io/969f3f3229a7c8b183ecc81bf87f2cebf8d85a3d62f960489d7ab58875bac6c5-image.png" align="center" width="600px" />

#### 2. Select conditions

Optionally define conditions to filter which alerts match this rule, targeting specific alert types, priority levels, repositories, or other attributes.

<Image src="https://files.readme.io/0b011148fc7846cd26e4958bcf3e1aa2a73e8f5e250201c3da10a725bcbd26aa-image.png" align="center" width="600px" />

#### 3. Select project

Choose the Linear connection and where issues should be created:

* **Integration** — Select which connected Linear workspace to use.
* **Team** — Select the Linear team that issues will be created in.

<Image src="https://files.readme.io/83a2c43f4da7a690d295f8ffb84434f444c9af9355447d7a24b2d14b2c5870c7-image.png" align="center" width="600px" />

#### 4. Configure issue

Define how the Linear issue should be created:

* **Priority** — Set a specific priority, or use **Auto** to map the alert priority to a Linear priority automatically.
* **Labels** — Optionally add labels to created issues.
* **Assignee** – Optionally add an assignee using email or display name.

<Image src="https://files.readme.io/eb8b966febb210d99bbb5edd2c9b6703321b6503811903611490c31c0ab4e45b-image.png" align="center" width="600px" />

Note: additional settings are not supported for Linear.

#### 5. Configure actions

Define what happens when alert state changes, such as creating a new issue when conditions are met and updating the linked issue when the alert changes.

<Image src="https://files.readme.io/3ece6b55ea3bbc084dcf1bca4407702e5c9706b9e2be59da066aa50819546c3f-image.png" align="center" width="600px" />

<br />

After reviewing the summary, click **Create** to activate the rule.

<Image src="https://files.readme.io/a8f62a7b5ff527f3b955cc57483f84e3e85717f574080311261a2d05233256b0-image.png" align="center" width="600px" />

## Permissions

### Socket roles

| Role        | Capabilities                                   |
| ----------- | ---------------------------------------------- |
| Owner       | Connect, disconnect, configure ticketing rules |
| Admin       | Connect, disconnect, configure ticketing rules |
| Member      | View connections, create issues from alerts    |
| Contributor | View connections                               |

### Linear app permissions

When you authorize the integration, Socket requests permission to read workspace data and to create and update issues and comments for the teams you select. Socket does not access data outside the workspace and teams you authorize.

## Troubleshooting

<Accordion title="The authorization window doesn't open" icon="fa-info-circle">
Your browser may be blocking popups. Allow popups for the Socket dashboard, or copy the installation link from the Connect dialog and open it in a new browser tab.
</Accordion>

<Accordion title="The connection shows an Error or revoked status" icon="fa-info-circle">
The access granted to Socket may have been revoked in Linear, or the token may have expired. Remove the connection in **Settings → Integrations → Linear** and connect again.
</Accordion>

<Accordion title="Issues are not being created automatically" icon="fa-info-circle">
Verify the following:

1. The ticketing rule is set to **Active** status.
2. The Linear workspace is still connected (check **Settings → Integrations → Linear**).
3. The alert event matches the rule's event and condition filters.
4. The selected Linear team and project are still valid in your workspace.
</Accordion>

<Accordion title="I cannot complete the connection" icon="fa-info-circle">
Only users with **Owner** or **Admin** roles in the Socket organization can connect or disconnect the integration. If you have a different role, ask an administrator to complete the connection.
</Accordion>

<Accordion title="I have another problem" icon="fa-info-circle">
If you encounter problems or have questions not explained here, [contact support](https://docs.socket.dev/docs/contact-support).
</Accordion>

### Known issues and limitations

<Accordion title="Server error after connection" icon="fa-info-circle">
After completing the authorization in Linear you are met with a "Server error" page. This error __does not__ prevent the connection from completing and is purely a cosmetic error. There's a fix coming out shortly.
</Accordion>

<Accordion title="Additional fields has no effect" icon="fa-info-circle">
The additional fields under "Advanced settings" in the ticketing configuration has no effect on tickets being created. These are not yet fully wired up. This feature is coming very soon.
</Accordion>

## Next steps

* [Webhooks](https://docs.socket.dev/docs/webhooks) — Set up webhooks to receive real-time notifications for alert events.
* [Customizable Security Policies](https://docs.socket.dev/docs/enabled-issues) — Configure which alert types trigger warnings and blocks across your organization.
* [Organization Alerts](https://docs.socket.dev/docs/organization-alerts) — Review and manage alerts across all repositories in your organization.

<br />