​
Supported Features and Limitations

The Linear connector allows you to index and search Linear Issues and Project Documents from your Linear workspace. The connector leverages the Linear GraphQL API to bring updated information into Glean and enforce appropriate team and document permissions.

​
Supported Objects/Entities

Object TypeDescription
Linear IssuesItems created to track work or bugs
Issue CommentsComments added to Linear Issues
Project DocumentsDocuments associated with Linear Projects

​
Supported API Endpoints/Features

  • Linear GraphQL API (for crawling Issues, Comments, Documents)

​
Limitations

  • Indexing of private teams, issues, and documents requires a paid Linear plan (Standard or Plus tier). The connector cannot access private teams in the free plan.
  • Webhooks are not supported.
  • No audit API. Only data changes (not user views or edits) are supported for activity tracking.

​
Crawling Strategy

Crawl typeFull CrawlIncremental CrawlPeople DataActivityUpdate RateNotes
Issues & CommentsYesYes (filter by updatedAt)Yes (users API)No audit APIDaily (by default)-
Project DocumentsYesLimitedN/AN/ADailyThe connector performs a daily re-sync for documents; some updates/deletions may require a full crawl.
  • Full crawls query for all objects and comments.

​
Results Display

Search results for indexed Linear content in Glean include:
  • Issue title, description, assignee, status, priority, labels, project, author, and team
  • Commenter and related issue for comments
  • Project document title and author
Results respect the visibility and permissions set in Linear – only content you’re allowed to view in Linear will appear in Glean search.

​
Requirements

​
Access and plan

  • Linear administrator-level access within your workspace, including the ability to create a custom OAuth application for authentication. You must provide correct credentials and enable the necessary permissions.
  • Linear workspace plan on Standard or Plus if you need access to private teams and documents. Access to private team content is limited unless the appropriate permissions and plan tier are present.

​
APIs and credentials

  • Linear GraphQL API access and the ability to register a custom OAuth application.
  • OAuth2 credentials: Client ID and Client Secret obtained from your Linear OAuth application.

​
Permissions and scopes

  • Admin authorization for identity and document access.
  • You need an admin role in Linear for setup and to access identity information via APIs. While the admin scope is not strictly required, it’s highly recommended for authorization.
    • Scopes Required:
      • admin (read/write to public teams; may limit access to private team issues)
      • read (granular, per-user read-only access)
    • Note: Access is limited for private team content unless the appropriate permissions and plan tier are present.

​
Connect to Linear

This section walks you through the steps to connect your Glean instance to your Linear workspace. This process requires administrator access to both your Glean Admin Console and your Linear account.

​
Step 1: Register a New OAuth2 Application in Linear

First, you’ll need to create a new application in Linear to generate the necessary credentials for Glean.
  1. Sign in to your Linear workspace as an admin.
  2. Navigate to the Create a new OAuth2 Application page. Refer to Linear’s API documentation and OAuth setup guide for additional details.
  3. On the Create new application page, fill in the following details:
    • Application Name: Glean Application
    • Developer Name: Glean
    • Developer URL: https://glean.com
    • Callback URLs: https://[your-domain]-be.glean.com/instance/linear/oauth/verify_code
      • Note: Replace [your-domain] with your company’s unique Glean domain.
  4. Click the Create application button.

​
Step 2: Upload Keys and Authorize Glean

After creating the application in Linear, you will receive the Client ID and Client Secret. You will use these to complete the connection in Glean.
  1. From the Linear application details page, copy the Client ID and Client Secret.
  2. In your Glean Admin Console, navigate to the Linear connector setup page.
  3. Paste the Client ID and Client Secret into the corresponding fields.
  4. Click the Authorize button. A new browser tab will open for you to complete the authorization process.
  5. Follow the prompts to authorize Glean to access your Linear instance.
Upon successful authorization, the connection is established, and Glean can begin indexing your Linear data.

​
Permissions & Security

​
Data and Metadata Ingested

The connector ingests:
  • Linear Issues (including fields like title, description, status, assignee, labels, project, author, and team)
  • Issue Comments (including commenter and related issue)
  • Project Documents (title, author, content, and associated project)
  • User identity data for permissions mapping

​
Permission Propagation Logic

  • Content visibility in Glean depends on the permission model in Linear:
    • Issues and comments in public teams are visible to all relevant users.
    • Issues and comments in private teams are visible only to team members.
    • Project documents are visible to project members and associated teams.
    • Admins do NOT have access to private team issues unless they are explicitly added to those teams.

​
Security & Compliance Notes

  • Authentication is via OAuth2 with client credentials.
  • All API requests use the access token as a bearer token.
  • Permissions rely solely on what is enforced and returned by the Linear API; Glean does not override these behaviors.

​
Known Security Restrictions

  • Multi-instance Linear deployments are not supported.
  • All Linear content indexed is subject to Linear permissions, so “domain access” and “anonymous access” are not applicable.
  • No support for link-based access or anonymous content viewing.

​
Data Privacy Implications

  • Only authorized identity data and documents are indexed.
  • User and document visibility strictly follow Linear’s permission model to minimize exposure of sensitive content.