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

# Set up a Ramp connector

> C1 provides identity governance and just-in-time provisioning for Ramp. Integrate your Ramp instance with C1 to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access.

<Tip>
  **This is an updated and improved version of the Ramp connector!** If you're setting up Ramp with C1 for the first time, you're in the right place.
</Tip>

## Capabilities

| Resource          | Sync                                                          | Provision                                                     |
| :---------------- | :------------------------------------------------------------ | :------------------------------------------------------------ |
| Accounts          | <Icon icon="square-check" iconType="solid" color="#c937ae" /> | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |
| Roles             | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |                                                               |
| Vendors           | <Icon icon="square-check" iconType="solid" color="#c937ae" /> | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |
| Vendor agreements | <Icon icon="square-check" iconType="solid" color="#c937ae" /> |                                                               |

<Note>
  **Vendor owner is single-assignee.** Each Ramp vendor can have only one owner at a time. Granting the vendor owner entitlement to a new user overwrites the previous owner in Ramp — the prior owner is silently removed. Revoking the entitlement clears the owner only when the principal being revoked is the current owner.
</Note>

Synced Ramp vendors are emitted as C1 vendor resources with Ramp vendor identity metadata. Vendor owner access is represented as the `owner` entitlement on each vendor. Vendor agreements are available as an opt-in resource type and use the same Ramp `vendors:read` scope as vendors.

The Ramp connector supports [automatic account provisioning](/product/admin/account-provisioning).

### Connector actions

Connector actions are custom capabilities that extend C1 automations with app-specific operations. You can use connector actions in the [Perform connector action](/product/admin/automations-steps-reference#perform-connector-action) automation step.

| Action name   | Additional fields            | Description                                                                                                                            |
| ------------- | ---------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| disable\_user | `user_id` (string, required) | Deactivate a Ramp user. The user will no longer be able to log in, spend on cards, or receive notifications.                           |
| enable\_user  | `user_id` (string, required) | Reactivate a Ramp user. The user can log in to Ramp again, spend on their previously issued cards, and resume receiving notifications. |

## Gather Ramp credentials

<Warning>
  To configure the Ramp connector, you need the **Administrator** role in Ramp.
</Warning>

The Ramp connector supports two authentication methods. Choose the one that fits your setup:

### Option 1: Use an access token

<Steps>
  <Step>
    In Ramp, navigate to **Settings** > **Developers** > **API tokens**.
  </Step>

  <Step>
    Click **Create a token**, give it a name (for example, `ConductorOne`), and select the following scopes:

    * `users:read` — sync users and roles
    * `vendors:read` — sync vendors and vendor agreements

    If you enable provisioning, also select:

    * `users:write` — provision and deprovision users
    * `vendors:write` — grant and revoke vendor ownership

    If you enable audit-log event polling, also select:

    * `audit_logs:read` — read Ramp audit-log events for incremental sync

    <Warning>
      The **users:write** and **vendors:write** scopes are used only when C1 provisions and deprovisions access. **If you do not want C1 to perform these tasks, do not grant these scopes.**
    </Warning>
  </Step>

  <Step>
    Click **Create** and copy the token. Save it somewhere secure — you won't be able to view it again.
  </Step>
</Steps>

For more information, see the [Ramp API token documentation](https://docs.ramp.com/developer-api/v1/authorization).

### Option 2: Use OAuth 2.0 client credentials

<Steps>
  <Step>
    In Ramp, navigate to **Settings** > **Developers** > **OAuth apps**.
  </Step>

  <Step>
    Click **Create OAuth app** and configure the following:

    1. Enter a name: `ConductorOne`
    2. Set the grant type to **Client Credentials**
    3. Select the following scopes:

       * `users:read` — sync users and roles
       * `vendors:read` — sync vendors and vendor agreements

       If you enable provisioning, also select:

       * `users:write` — provision and deprovision users
       * `vendors:write` — grant and revoke vendor ownership

       If you enable audit-log event polling, also select:

       * `audit_logs:read` — read Ramp audit-log events for incremental sync

    <Warning>
      The **users:write** and **vendors:write** scopes are used only when C1 provisions and deprovisions access. **If you do not want C1 to perform these tasks, do not grant these scopes.**
    </Warning>

    4. Click **Create**
  </Step>

  <Step>
    Copy and save the **Client ID** and **Client Secret**. Save them somewhere secure — the secret won't be shown again.
  </Step>
</Steps>

For more information, see the [Ramp authorization documentation](https://docs.ramp.com/developer-api/v1/authorization).

## Configure the Ramp connector

<Warning>
  To complete this task, you'll need:

  * The **Connector Administrator** or **Super Administrator** role in C1
  * The **Administrator** role in Ramp
</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 **Ramp** and click **Add**.
      </Step>

      <Step>
        Choose how to set up the new Ramp 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>
        Select your authentication method and enter the credentials you gathered earlier:

        * **Access Token**: paste your Ramp API access token into the **Ramp Access Token** field.
        * **OAuth 2.0 Client Credentials**: paste your Ramp OAuth client ID and client secret into the **Ramp OAuth Client ID** and **Ramp OAuth Client Secret** fields.
      </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 Ramp connector is now pulling access data into C1.
  </Tab>

  <Tab title="Self-hosted">
    **Follow these instructions to use the Ramp 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

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

    ### Step 1: Set up a new Ramp 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 Ramp 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 Ramp connector deployment.

    The Ramp connector supports two authentication methods — pick one when populating the secret:

    * **Access Token** — a long-lived Ramp API access token.
    * **OAuth 2.0 Client Credentials** — a Ramp OAuth client ID and secret (the connector exchanges them for a short-lived access token automatically, via `https://api.ramp.com/developer/v1/token`).

    See the [Ramp authorization docs](https://docs.ramp.com/developer-api/v1/authorization) for how to create an OAuth app with the `Client Credentials` grant type and the following scopes:

    * **Required for read-only sync**: `users:read`, `vendors:read`.
    * **Required only if `BATON_PROVISIONING=true`**: `users:write`, `vendors:write`.
    * **Required only if `BATON_AUDIT_LOG_EVENTS=true`**: Ramp audit-log API availability, such as Ramp Plus, and the `audit_logs:read` scope.

    The connector points at `https://api.ramp.com` by default. Set `BATON_RAMP_BASE_URL` (or the **Ramp API Base URL** field) to `https://demo-api.ramp.com` (or another Ramp environment) to override.

    ### Optional resources and events

    The connector ships with an opt-in `vendor_agreement` resource type. When enabled in C1 resource-type settings, the connector syncs Ramp vendor agreements as their own resources, including term, renewal status, total contract value, and contract owners. Vendor agreements use the existing `vendors:read` scope; Ramp does not require a separate vendor-agreement scope.

    Ramp vendors are always decorated with cross-system identity and pre-aggregated trailing-window spend when those fields are returned by Ramp.

    Set `BATON_AUDIT_LOG_EVENTS=true` to expose Ramp's audit-log API as an event feed so vendor and agreement changes can flow into C1 incrementally between full syncs. This setting is independent from vendor-agreement resource enablement and requires Ramp audit-log API availability, such as Ramp Plus, plus the `audit_logs:read` scope. When the flag is unset (the default), the audit-log API is not called.

    #### Secrets configuration

    **Option A — Access Token:**

    ```yaml expandable theme={"theme":{"light":"css-variables","dark":"css-variables"}}
    # baton-ramp-secrets.yaml
    apiVersion: v1
    kind: Secret
    metadata:
      name: baton-ramp-secrets
    type: Opaque
    stringData:
      # C1 credentials
      BATON_CLIENT_ID: <C1 client ID>
      BATON_CLIENT_SECRET: <C1 client secret>

      # Ramp credentials
      BATON_TOKEN: <Ramp API access token>

      # Optional: include if you want C1 to provision access using this connector
      BATON_PROVISIONING: "true"

      # Optional: include if you want audit-log incremental sync events.
      # Requires Ramp audit-log API availability, such as Ramp Plus.
      BATON_AUDIT_LOG_EVENTS: "true"
    ```

    **Option B — OAuth 2.0 Client Credentials:**

    ```yaml expandable theme={"theme":{"light":"css-variables","dark":"css-variables"}}
    # baton-ramp-secrets.yaml
    apiVersion: v1
    kind: Secret
    metadata:
      name: baton-ramp-secrets
    type: Opaque
    stringData:
      # C1 credentials
      BATON_CLIENT_ID: <C1 client ID>
      BATON_CLIENT_SECRET: <C1 client secret>

      # Ramp OAuth credentials
      BATON_RAMP_CLIENT_ID: <Ramp OAuth client ID>
      BATON_RAMP_CLIENT_SECRET: <Ramp OAuth client secret>

      # Optional: include if you want C1 to provision access using this connector
      BATON_PROVISIONING: "true"

      # Optional: include if you want audit-log incremental sync events.
      # Requires Ramp audit-log API availability, such as Ramp Plus.
      # When set, the OAuth client must also have the `audit_logs:read` scope.
      BATON_AUDIT_LOG_EVENTS: "true"
    ```

    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-ramp.yaml
    apiVersion: apps/v1
    kind: Deployment
    metadata:
      name: baton-ramp
      labels:
        app: baton-ramp
    spec:
      selector:
        matchLabels:
          app: baton-ramp
      template:
        metadata:
          labels:
            app: baton-ramp
            baton: "true"
            baton-app: ramp
        spec:
          containers:
          - name: baton-ramp
            image: public.ecr.aws/conductorone/baton-ramp:latest
            imagePullPolicy: IfNotPresent
            env:
            - name: BATON_HOST_ID
              value: baton-ramp
            envFrom:
            - secretRef:
                name: baton-ramp-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 Ramp connector to. Ramp data should be found on the **Entitlements** and **Accounts** tabs.
      </Step>
    </Steps>

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