> ## 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 PropelAuth connector

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

C1 provides identity governance for PropelAuth. Integrate your PropelAuth
environment with C1 for unified visibility and governance over the users in
your project, the organizations they belong to, and the role each user holds in
each organization. The connector is read-only — it never writes to PropelAuth.

## Capabilities

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

Organization membership and each member's organization role are synced as
access grants on the organization.

## Gather PropelAuth credentials

<Warning>
  To configure the PropelAuth connector, you need access to your PropelAuth
  dashboard with permission to create a Backend Integration API key for the
  environment you want to sync.
</Warning>

PropelAuth keeps each environment (test, staging, production) separate, with
its own Auth URL and its own API keys. Configure one connector per environment.

<Steps>
  <Step>
    Sign in to the [PropelAuth dashboard](https://app.propelauth.com/) and
    select the project and environment you want to connect.
  </Step>

  <Step>
    Open **Backend Integration** and copy the environment's **Auth URL**. Test
    environments use an auto-issued `*.propelauthtest.com` address; production
    uses your configured custom auth domain (for example
    `https://auth.yourcompany.com`).
  </Step>

  <Step>
    Still under **Backend Integration**, open **API Keys** and create a new
    API key for this environment. Copy the key — it is shown once. The
    connector only reads, so no additional scopes or roles need to be granted.
  </Step>
</Steps>

## Configure the PropelAuth 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 **PropelAuth** and click **Add**.
      </Step>

      <Step>
        Choose how to set up the new PropelAuth 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 PropelAuth credentials:

        * **Auth URL**: Your PropelAuth environment's Auth URL from Backend Integration.
        * **API Token**: The Backend Integration API key you created for this environment.
      </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 PropelAuth connector is now pulling access data into C1.
  </Tab>

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

    <Steps>
      <Step>
        Create secrets for the PropelAuth credentials.
      </Step>

      <Step>
        Configure the connector environment variables:

        * **Auth URL**: Your PropelAuth environment's Auth URL from Backend Integration.
        * **API Token**: The Backend Integration API key for this environment (store as a secret).
      </Step>

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

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