Set up a Linear connector

C1 provides identity governance and just-in-time provisioning for Linear. Integrate your Linear instance with C1 to run user access reviews (UARs) and enable just-in-time access requests.

Capabilities

Resource	Sync	Provision
Accounts
Organizations
Teams
Projects
Roles

This connector can also be configured to automatically create and update Linear tickets to track manual provisioning assignments. Go to Configure Linear as an external ticketing provider to learn more.

Gather Linear credentials

Configuring the connector requires you to pass in credentials generated in Linear. Gather these credentials before you move on.

Prerequisites

The user who generates the API key must have the Admin or Owner role in the Linear workspace. The API key inherits all permissions of the user who creates it.

If provisioning is enabled (inviting users, suspending users, managing team membership), the key creator must have Admin or Owner access.

Generate a new Linear API key

1. In Linear, click your profile photo and select Settings.

2. Click Security & access.

3. In the Personal API keys section of the page, enter a label such as “C1” and click Create key.

4. The new API key is generated for you. Carefully copy and save the API key.

   Linear only displays the API key once. If you lose it, you must delete the key and create a new one.

Validate your API key

After creating your API key, verify it works before configuring the connector.

1. Open a terminal and run the following command, replacing <your-api-key> with your key:

   curl -s -H "Authorization: <your-api-key>" \
     -H "Content-Type: application/json" \
     -d '{"query":"{ viewer { id name email } }"}' \
     https://api.linear.app/graphql
   
2. A successful response returns your user details:

   {"data":{"viewer":{"id":"...","name":"Your Name","email":"[e-mail]"}}}
   

   If you see an authentication error, verify that you copied the full API key and that the key has not been revoked.

Done. Next, move on to the connector configuration instructions.

Configure the Linear connector

To complete this task, you’ll need:

• The Connector Administrator or Super Administrator role in C1
• Access to the set of Linear credentials generated by following the instructions above

Cloud-hosted

Follow these instructions to use a built-in, no-code connector hosted by C1.

1. In C1, navigate to Integrations > Connectors and click Add connector.

2. Search for Linear and click Add.

3. Choose how to set up the new Linear connector:

   • Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren’t yet managed with C1)

   • Add the connector to a managed app (select from the list of existing managed apps)

   • Create a new managed app

4. Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of C1 users. Setting multiple owners is allowed.

   If you choose someone else, C1 will notify the new connector owner by email that their help is needed to complete the setup process.

5. Click Next.

6. Find the Settings area of the page and click Edit.

7. Paste the API key into the API key field.

8. Optional. If you want to skip syncing projects, click to enable Skip projects.

9. Optional. If you want to automatically create Linear tickets to track provisioning tasks, click Enable external ticket provisioning. Learn more about external ticketing system integrations.

10. Optional. Enter a list of team IDs that will be used for ticket schemas in the Teams field.

11. Click Save.

12. The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.

Done. Your Linear connector is now pulling access data into C1.

Self-hosted

Follow these instructions to use the Linear connector, hosted and run in your own environment.

When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with C1, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1 UI for access reviews and access requests.

Resources

• Official download center: For stable binaries (Windows/Linux/macOS) and container images.

• GitHub repository: Access the source code, report issues, or contribute to the project.

Step 1: Set up a new Linear connector

1. In C1, navigate to Integrations > Connectors > Add connector.

2. Search for Baton and click Add.

3. Choose how to set up the new Linear connector:

   • Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren’t yet managed with C1)

   • Add the connector to a managed app (select from the list of existing managed apps)

   • Create a new managed app

4. Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of C1 users. Setting multiple owners is allowed.

   If you choose someone else, C1 will notify the new connector owner by email that their help is needed to complete the setup process.

5. Click Next.

6. In the Settings area of the page, click Edit.

7. Click Rotate to generate a new Client ID and Secret.

   Carefully copy and save these credentials. We’ll use them in Step 2.

Step 2: Create Kubernetes configuration files

Create two Kubernetes manifest files for your Linear connector deployment:

Secrets configuration

# baton-linear-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-linear-secrets
type: Opaque
stringData:
  # C1 credentials
  BATON_CLIENT_ID: <C1 client ID>
  BATON_CLIENT_SECRET: <C1 client secret>

  # Linear credentials
  BATON_API_KEY: <API key for Linear>

  # Optional: include if you want C1 to provision access using this connector
  BATON_PROVISIONING: true

  # Optional: include if you want C1 to skip syncing projects
  BATON_SKIP_PROJECTS: true

  # Optional: include if you want C1 to create provisioning tickets in Linear 
  BATON_TICKETING: true
  BATON_TICKET_SCHEMA_TEAM_IDS_FILTER: <(Optional.) List of Linear team IDs>

See the connector’s README or run --help to see all available configuration flags and environment variables.

Deployment configuration

# baton-linear.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-linear
  labels:
    app: baton-linear
spec:
  selector:
    matchLabels:
      app: baton-linear
  template:
    metadata:
      labels:
        app: baton-linear
        baton: true
        baton-app: linear
    spec:
      containers:
        - name: baton-linear
          image: public.ecr.aws/conductorone/baton-linear:latest
          imagePullPolicy: IfNotPresent
        env:
        - name: BATON_HOST_ID
          value: baton-linear
          envFrom:
            - secretRef:
                name: baton-linear-secrets

Step 3: Deploy the connector

1. Create a namespace in which to run C1 connectors (if desired), then apply the secret config and deployment config files.

2. Check that the connector data uploaded correctly. In C1, click Apps. On the Managed apps tab, locate and click the name of the application you added the Linear connector to. Linear data should be found on the Entitlements and Accounts tabs.

Done. Your Linear connector is now pulling access data into C1.

Troubleshooting Linear authentication

The connector fails to authenticate

The connector validates your API key at startup by querying the Linear API. If you see failed to authenticate in the connector logs:

1. Verify the API key is correct and has not been revoked. In Linear, go to Settings > Security & access > Personal API keys and check that the key is still listed.
2. Generate a new API key if needed and update the connector configuration.

The connector cannot provision access

If sync works but provisioning operations fail, the API key may belong to a user without sufficient permissions:

1. Verify the user who created the API key has the Admin or Owner role in Linear.
2. Members and Guests cannot perform provisioning operations such as inviting users, suspending accounts, or managing team membership.
3. If needed, have an Admin or Owner generate a new API key.