Skip to main content

Configure Advanced User Attribute Mapping

  • Nov 18, 2026 10:33 PM UTC
  • 0 replies
  • 3 views

Dawn Wayland
Employee
Forum|alt.badge.img+9

Synchronize additional user profile attributes from Entra ID or Okta to Appspace.

 

Standard Appspace identity provisioning includes common user information such as email address, first name, and last name. Additional profile information such as phone number, department, and job title can also be provisioned.

Organizations that need additional profile fields can configure custom SCIM attribute mappings from Microsoft Entra ID or Okta.

Important: Confirm the source attribute and the Appspace profile property you want to synchronize before changing your identity provider configuration.

 

Configure a custom attribute in Microsoft Entra ID

 

  1. Open the Appspace SSO + SCIM enterprise application in Entra ID.
  2. Open Provisioning.
  3. Select Attribute Mapping.
  4. Select Users.
  5. Enable Show advanced options.
  6. Select Edit attribute list.
Entra Show advanced options and Edit attribute list

 

Add the Appspace SCIM attribute using the following format:

urn:ietf:params:scim:schemas:extension:appspace:2.0:User:[attribute]

Replace [attribute] with the user attribute you want to map to Appspace.

For example, to map a mobile phone attribute:

urn:ietf:params:scim:schemas:extension:appspace:2.0:User:mobile

Entra custom SCIM attribute using the Appspace extension namespace

 

Test the Entra ID mapping

 

  1. Save the attribute configuration.
  2. Use Provision on demand.
  3. Select a test user or small group.
  4. Run provisioning.
  5. Confirm that the new value synchronizes successfully before expanding the change.

Configure a custom attribute in Okta

 

  1. Open the Appspace application in Okta.
  2. Go to Provisioning.
  3. Open the Profile Editor.
  4. Select Add Attribute.
Okta Profile Editor highlighting Add Attribute

 

Configure the Okta attribute

 

For a string-based profile field, configure the attribute using the appropriate value from your environment.

Use the following external namespace:

urn:ietf:params:scim:schemas:extension:appspace:2.0:User

For example, when mapping a mobile phone field:

  • Data type: String
  • Display name: Mobile
  • Variable name: mobile
  • External name: mobile
  • External namespace: urn:ietf:params:scim:schemas:extension:appspace:2.0:User
  • Scope: User personal

Replace Mobile and mobile with the display name and property required for the user attribute you are configuring.

Okta Add Attribute dialog showing Mobile example and Appspace external namespace

 

Map the Okta attribute to Appspace

 

  1. Save the new attribute.
  2. Select Mappings.
  3. Select the Okta-to-Appspace user mapping.
  4. Map the appropriate Okta user property to the Appspace attribute.
  5. Save the mapping.
Okta User Profile Mappings showing mobile attribute mapped to the Appspace profile

 

Add the profile field in Appspace

If the custom property also needs to appear in the Appspace user profile:

  1. Go to Users > Settings > User Profile.
  2. Select Add.
  3. Enter the appropriate display name.
  4. Set Source to SCIM / SAML.
  5. Enter the same property name used in the identity provider mapping.
  6. Select the appropriate input type.
  7. Select an appropriate icon.
  8. Save the field.

For example, a mobile phone profile field may use:

  • Display Name: Mobile
  • Source: SCIM / SAML
  • Property: mobile
  • Input Type: String
  • Icon: Phone
Appspace Add Field dialog showing Mobile as a SCIM/SAML profile property

 

Verify the synchronized attribute

After synchronization completes, open the profile of a provisioned user and confirm that the custom attribute appears with the expected value.

Appspace user profile Attributes tab showing the synchronized Mobile value

 

If the attribute does not appear, verify that the identity provider mapping and Appspace property name match exactly.