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

# Set up a Workable connector

> C1 provides identity governance for Workable. Integrate your Workable account with C1 for unified visibility and governance over member access.

C1 provides identity governance for Workable. Integrate your Workable account
with C1 for unified visibility and governance over the members who can access
your recruiting and HR data.

## Capabilities

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

The connector syncs Workable members as users. Both active and deactivated
members are synced; a deactivated member is recorded as disabled. Each member's
recruiting role and HR role are recorded as informational attributes on the
user. Workable does not expose roles as a separate, governable resource, so
roles are not synced on their own.

## Gather Workable credentials

<Warning>
  You need an administrator account on your Workable instance to create an API
  access token.
</Warning>

<Steps>
  <Step>
    Sign in to Workable and open **Settings** > **Integrations** > **API access
    tokens** (Workable's API access token area).
  </Step>

  <Step>
    Create an access token with the **`r_jobs`** scope. Members are read through
    the `r_jobs` scope; there is no separate `r_members` scope.
  </Step>

  <Step>
    Copy two values: your **account subdomain** (the `<subdomain>` part of your
    `https://<subdomain>.workable.com` URL) and your **access token**.
  </Step>
</Steps>

## Configure the Workable 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 **Apps** > **Connectors** and click **Add connector**.
      </Step>

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

      <Step>
        Choose where to add the connector: **Create a new app**, or **Add to an existing app** (then select the app).

        If you're creating a new app, choose whether to link it to an application discovered from your identity provider: select **Yes** and pick the IdP application, or **No** to continue with just the connector.
      </Step>

      <Step>
        Set the connector's **Name** and, optionally, a **Description**.
      </Step>

      <Step>
        Click the pencil icon next to **Owners** to choose who can configure and manage this connector.
      </Step>

      <Step>
        Click **Add**. The connector is created and its configuration page opens.
      </Step>

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

      <Step>
        Enter the Workable credentials:

        * **Account subdomain**: your account subdomain, e.g. `acme`.
        * **Access token**: the Workable API access token with the `r_jobs` scope.
      </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 Workable connector is now pulling access data into C1.
  </Tab>

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

    <Steps>
      <Step>
        Create a secret for the Workable access token.
      </Step>

      <Step>
        Configure the connector with:

        * **Account subdomain**: your account subdomain, e.g. `acme`.
        * **Access token**: the Workable API access token with the `r_jobs` scope (stored as a secret).
      </Step>

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

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