Set up SCIM mappings for custom user fields

Overview

Use SCIM custom field mappings to sync additional user attributes from your identity provider (IdP) to custom user fields in Ramp. Before you add mappings, connect SCIM and complete the prerequisites in your provider's setup guide, such as Before you begin for Okta or Before you begin for Microsoft Entra. For general SCIM setup and provisioning requirements, see Setting up SCIM and managing user provisioning.

Set up custom user fields with SCIM

Custom Fields can be integrated with SCIM to map additional attributes from your IdP to user profiles in Ramp. This allows you to maintain consistent custom data across systems and use it in Ramp workflows.

Step 1: Create custom fields in Ramp

Before mapping, you must create custom fields in Ramp.

To create custom fields, see Custom fields.

Step 2: Map IdP attributes to custom fields in Ramp

Once you’ve configured the mappings in your IdP, you need to connect them in Ramp:

From the People page, click the three-dot menu on the top right
Open the settings for your connected SCIM provider
Scroll down to the Custom field mappings section
Click Add mapping
Enter the SCIM attribute name:

For Okta: Use the “External name” you configured (e.g., budget_manager )
For Entra: Use only the attribute name after the Ramp namespace (e.g., approver from urn:ietf:params:scim:schemas:extension:ramp:2.0:User:approver )

Select the corresponding Ramp custom field from the dropdown
Click Save changes

Each custom field can only be mapped to one SCIM attribute. If you send attribute names in camelCase from your IdP (for example, userOrganization), Ramp will automatically convert them to snake_case (for example, user_organization).

The custom field values will sync automatically when users are provisioned or updated. Custom field data typically appears in Ramp within 5-10 minutes for Okta, or within 10 minutes for Microsoft Entra.

Step 3: Verify custom field sync

To confirm custom fields are syncing correctly:

Go to People in Ramp
Click on a user to view their profile
Verify the custom field data appears correctly

You can also populate custom field values through CSV upload.

Set up SCIM mappings in Okta

First, complete the initial Okta SCIM setup by following Set up Ramp’s SCIM integration with Okta. Once connected, return here to configure custom field mappings.

Configure custom field mappings in Okta

To map custom fields from Okta to Ramp:

In Okta, go to Applications > Ramp > Provisioning > To App
Under Attribute Mappings , click Go to Profile Editor
Click Add Attribute and configure:

Data type: Choose string or string array
Display name: User-friendly name (can be any value)
Variable name: Internal Okta name (can be any value)
External name: Must match your Ramp configuration in snake_case (for example, budget_manager )
External namespace: urn:ietf:params:scim:schemas:extension:ramp:2.0:User
Attribute required: Leave unchecked until testing is complete

Save the attribute
Return to Attribute Mappings and map Okta user profile attributes to your new custom attributes, or manually specify values for users
Set each mapping to apply on "Create and Update"

Set up SCIM mappings in Microsoft Entra

First, complete the initial Entra SCIM setup by following Set up Ramp's SCIM integration with Microsoft Entra. Once connected, return here to configure custom field mappings.

Configure custom field mappings in Entra

To add custom fields in Microsoft Entra:

In your Microsoft Entra, click Provisioning > Attribute mapping (Preview) > Provision Microsoft Entra ID Users
At the bottom of the screen, click Show advanced options > Edit attribute list for customappsso
Add your custom attribute with these settings:

Name: Prefix with Ramp namespace: urn:ietf:params:scim:schemas:extension:ramp:2.0:User: followed by your attribute name (e.g., urn:ietf:params:scim:schemas:extension:ramp:2.0:User:approver )
Type: String
Multi-Value? Check this box if the attribute contains multiple values

Save the configuration and navigate back to the Attribute mapping page
Click Add New Mapping below the table of existing attribute mappings
Configure the mapping using one of these methods:

Direct mapping: Select an existing Entra user profile attribute from the dropdown
Constant value: Enter a fixed value for all users
Expression: Create a custom expression (ensure arrays are used for multi-value attributes)

Save the mapping
Wait for automatic provisioning which happens about hourly. Or you can do on-demand provisioning for up to 5 users at once

Frequently asked questions

Which custom field types can be synced via SCIM?

The following custom field types can be synced through SCIM:

Ramp Object - References to other Ramp objects (for example, another user). Map using the associated user’s email address.
Select - Custom categories (for example, job title). Note: Values received from SCIM systems will automatically have a value for that option created in the Ramp system.
Boolean - Yes/no fields (for example, remote worker, has parking)
Text - Free-form text (for example, notes). Note: this field type has less workflow flexibility than Custom Object.

What happens if a custom field value is empty in the IdP?

Empty values will sync as blank in Ramp. Ensure your IdP data is complete before enabling SCIM sync for custom fields.

Can I map multiple IdP attributes to one custom field?

No. Each Ramp custom field maps to a single IdP attribute. Create separate custom fields if you need to track multiple attributes.

What data types are supported for custom fields in SCIM?

Ramp supports string (single value) and string array (multiple values/list). This configuration cannot be changed after the attribute is created in your IdP.

What naming convention must I use for custom field external names?

External names must be in snake_case format using only lowercase letters and underscores (for example, budget_manager, cost_center_owner). Display names and variable names in your IdP can be any value.

For general SCIM FAQs, see Setting up SCIM and managing user provisioning.