> ## Documentation Index
> Fetch the complete documentation index at: https://www.c1.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# 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      | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |                                                               |
| Organizations | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |                                                               |
| Teams         | <Icon icon="square-check" iconType="solid" color="#c937ae" /> | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |
| Projects      | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |                                                               |
| Roles         | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |                                                               |

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](/product/admin/external-ticketing#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.

### Generate a new Linear API key

<Steps>
  <Step>
    In Linear, click your profile photo and select **Settings**.
  </Step>

  <Step>
    Click **Security & access**.
  </Step>

  <Step>
    In the **Personal API keys** section of the page, enter a label such as "C1" and click **Create key**.
  </Step>

  <Step>
    The new API key is generated for you. Carefully copy and save the API key.
  </Step>
</Steps>

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

## Configure the Linear connector

<Warning>
  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
</Warning>

<Tabs>
  <Tab title="Cloud-hosted">
    **Follow these instructions to use a built-in, no-code connector hosted by C1.**

    <Steps>
      <Step>
        In C1, navigate to **Integrations** > **Connectors** and click **Add connector**.
      </Step>

      <Step>
        Search for **Linear** and click **Add**.
      </Step>

      <Step>
        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
      </Step>

      <Step>
        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.
      </Step>

      <Step>
        Click **Next**.
      </Step>

      <Step>
        Find the **Settings** area of the page and click **Edit**.
      </Step>

      <Step>
        Paste the API key into the **API key** field.
      </Step>

      <Step>
        **Optional.** If you want to skip syncing projects, click to enable **Skip projects**.
      </Step>

      <Step>
        **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.](/product/admin/external-ticketing)
      </Step>

      <Step>
        **Optional.** Enter a list of team IDs that will be used for ticket schemas in the **Teams** field.
      </Step>

      <Step>
        Click **Save**.
      </Step>

      <Step>
        The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing.
      </Step>
    </Steps>

    **Done.** Your Linear connector is now pulling access data into C1.
  </Tab>

  <Tab title="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](https://dist.conductorone.com/ConductorOne/baton-linear): For stable binaries (Windows/Linux/macOS) and container images.

    * [GitHub repository](https://github.com/conductorone/baton-linear): Access the source code, report issues, or contribute to the project.

    ### Step 1: Set up a new Linear connector

    <Steps>
      <Step>
        In C1, navigate to **Integrations** > **Connectors** > **Add connector**.
      </Step>

      <Step>
        Search for **Baton** and click **Add**.
      </Step>

      <Step>
        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
      </Step>

      <Step>
        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.
      </Step>

      <Step>
        Click **Next**.
      </Step>

      <Step>
        In the **Settings** area of the page, click **Edit**.
      </Step>

      <Step>
        Click **Rotate** to generate a new Client ID and Secret.

        Carefully copy and save these credentials. We'll use them in Step 2.
      </Step>
    </Steps>

    ### Step 2: Create Kubernetes configuration files

    Create two Kubernetes manifest files for your Linear connector deployment:

    #### Secrets configuration

    ```yaml expandable theme={"theme":{"light":"css-variables","dark":"css-variables"}}
    # 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

    ```yaml expandable theme={"theme":{"light":"css-variables","dark":"css-variables"}}
    # 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: ghcr.io/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

    <Steps>
      <Step>
        Create a namespace in which to run C1 connectors (if desired), then apply the secret config and deployment config files.
      </Step>

      <Step>
        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.
      </Step>
    </Steps>

    **Done.** Your Linear connector is now pulling access data into C1.
  </Tab>
</Tabs>