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

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

C1 provides identity governance for Mulesoft Anypoint Platform. Integrate your
Anypoint organization with C1 for unified visibility and governance over user,
team, and role group access.

## Capabilities

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

This connector is **read-only**: it syncs organization members, teams, role
groups, and their memberships through the Anypoint Access Management API and
does not provision changes back to Anypoint Platform.

## Gather Mulesoft credentials

<Warning>
  You need an Anypoint Platform account with permission to create Connected Apps
  and read organization members, teams, and role groups in Access Management.
</Warning>

<Steps>
  <Step>
    Sign in to Anypoint Platform and open **Access Management** > **Connected
    Apps**. Create a Connected App of type **App acts on its own behalf (client
    credentials)**.
  </Step>

  <Step>
    Grant the app read access to organization members, teams, and role groups,
    then save it. Copy the generated **Client ID** and **Client Secret**.
  </Step>

  <Step>
    Note your **Organization ID** from **Access Management** > **Organization**,
    and your control plane base URL: `https://anypoint.mulesoft.com` (US) or
    `https://eu1.anypoint.mulesoft.com` (EU).
  </Step>
</Steps>

## Configure the Mulesoft 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 **Mulesoft** 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 Mulesoft credentials:

        * **Client ID**: the Connected App client ID.
        * **Client secret**: the Connected App client secret.
        * **Organization ID**: the Anypoint organization ID to sync.
        * **Base URL**: your control plane URL, for example `https://anypoint.mulesoft.com`.
      </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 Mulesoft connector is now pulling access data into C1.
  </Tab>

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

    <Steps>
      <Step>
        Create a secret for the Connected App client secret.
      </Step>

      <Step>
        Configure the connector with the Connected App client ID, the client
        secret, the organization ID, and your control plane base URL.
      </Step>

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

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