> ## Documentation Index
> Fetch the complete documentation index at: https://conductorone-docs-mcp-bridge-private-server.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Set up a Plane connector

> C1 provides identity governance for Plane. Integrate your Plane instance with C1 for unified visibility and governance over user access.

C1 provides identity governance for Plane. Integrate your Plane workspace with
C1 for unified visibility and governance over who can access your workspace and
projects.

## Capabilities

| Resource          | Sync                                                          | Provision |
| ----------------- | ------------------------------------------------------------- | --------- |
| Workspace members | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |           |
| Workspace         | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |           |
| Projects          | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |           |

The connector syncs every member of the workspace as a user, the workspace
itself, and each project. It brings in workspace membership and project
membership as access grants, including the role held in each (Admin, Member, or
Guest).

## Gather Plane credentials

<Warning>
  You need a Plane account with access to the workspace you want to govern. The
  personal access token you create can see every workspace your account belongs
  to, so make sure you note the slug of the specific workspace you want C1 to
  sync.
</Warning>

<Steps>
  <Step>
    In Plane, open your **Profile settings** and select the **Personal access
    tokens** tab.
  </Step>

  <Step>
    Click **Add personal access token**, give it a title, and create it. Copy
    the generated token (it begins with `plane_api_`). Store it somewhere safe;
    Plane shows it only once.
  </Step>

  <Step>
    Note your **workspace slug**. It is the short identifier in your workspace
    URL — for example, in `https://app.plane.so/acme-co/` the slug is
    `acme-co`.
  </Step>
</Steps>

## Configure the Plane connector

<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 **Plane** and click **Add**.
      </Step>

      <Step>
        Choose how to set up the new Plane connector.
      </Step>

      <Step>
        Set the owner for this connector.
      </Step>

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

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

      <Step>
        Enter the Plane credentials:

        * **Base URL**: `https://api.plane.so` for Plane Cloud. For a
          self-hosted Plane instance, enter your own Plane domain.
        * **API key**: the personal access token you created (starts with
          `plane_api_`).
        * **Workspace slug**: the slug of the workspace you want to sync.
      </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 Plane connector is now pulling access data into C1.
  </Tab>

  <Tab title="Self-hosted">
    Follow these instructions to run the Plane connector in your own
    environment.

    <Steps>
      <Step>
        Create a secret for your Plane personal access token.
      </Step>

      <Step>
        Configure the connector with these values:

        * **Base URL**: `https://api.plane.so` for Plane Cloud, or your own
          domain for a self-hosted Plane Community Edition instance.
        * **API key**: your Plane personal access token.
        * **Workspace slug**: the slug of the workspace you want to sync.
      </Step>

      <Step>
        Deploy the connector using your standard self-hosted connector process.
      </Step>
    </Steps>

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