SCIM User Attribute Update Settings

Edited

Overview

Fluid's SCIM integration can automatically update user attributes in Fluid whenever a corresponding value changes in your identity provider (IdP — e.g. Microsoft Entra ID or Okta).

📘 Note These SCIM attribute mapping settings are disabled by default. As they allow SCIM to overwrite Fluid fields, most clients should validate and consolidate their Active Directory data beforehand to avoid syncing inaccurate values. To have attribute mapping enabled for your environment, please contact Fluid Support at support@fluid.work or your Fluid Success Manager.

When your IdP provisions or updates a user, it sends the user's attributes to Fluid inside the SCIM enterprise extension block:

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

Fluid reads the attributes from this block and writes them to the matching Fluid fields.

⚠️ Important SCIM writes access to that Fluid field. Any manual edits made directly in Fluid to a field controlled by SCIM may be overwritten on the next SCIM sync.


Configurable Attributes

Map the following SCIM attribute names in your IdP. Note that the SCIM attribute name often differs from the Fluid field name it updates. Attribute names are matched case-insensitively, and a value is only written when it is non-empty and differs from the current value in Fluid.

Core schema attributes

These come from the SCIM core user schema (urn:ietf:params:scim:schemas:core:2.0:User), not the enterprise extension.

Setting

SCIM Source Attribute

Fluid Field Updated

Description

First Name and Last Name

name.givenName, name.familyName

First Name, Last Name

Sets the Fluid user's first and last name.

Email

emails

Email Address

Sets the Fluid user email address from the SCIM email value.

Display Name

displayName

Display Name

Sets the Fluid user display name.

Enterprise extension attributes

These are sent inside the urn:ietf:params:scim:schemas:extension:enterprise:2.0:User block.

Setting

SCIM Source Attribute

Fluid Field Updated

Description

Employee ID

employeeNumber

Reference

Updates the Reference value in Fluid based on the SCIM employeeNumber value.

Role

role

User Role

Sets the Fluid user role from the SCIM role attribute.

Cost Centre

costCenter

Cost Centre

Sets the Fluid user cost centre from the SCIM costCenter value.

Manager

manager / managerId

Manager

Sets the Fluid user manager from the SCIM manager attribute. Accepts either an object (manager.value) or a plain string; the value is resolved to a Fluid user by ID, username, display name, or email.

Organization

organization

Team

Sets the Fluid active resource plan Team from the SCIM Team value.

Division

division

Division

Sets the Fluid active resource plan division from the SCIM division value.

Department

department

Department

Sets the Fluid active resource plan department from the SCIM department value.

Country

country

Country

Sets the Fluid user country directly from a dedicated SCIM country value.

Region

region

Location

Sets the Fluid user location directly from a dedicated SCIM region value.

Rate Card

rateCard

Classification

Sets the Fluid user classification from the SCIM rateCard value.

Engagement Type

engagementType

Engagement Type

Sets the Fluid user engagement type from the SCIM engagementType value.


Example Payload

{
  "schemas": [
    "urn:ietf:params:scim:schemas:core:2.0:User",
    "urn:ietf:params:scim:schemas:extension:enterprise:2.0:User"
  ],
  "userName": "jane.smith@contoso.com",
  "active": true,
  "urn:ietf:params:scim:schemas:extension:enterprise:2.0:User": {
    "costCenter": "4130",
    "division": "Platform",
    "department": "Software Development",
    "organization": "Engineering",
    "employeeNumber": "701984"
  }
}

Result: costCenter → Cost Centre, division → division department → department, organization → team, employeeNumber → Reference.


Mapping to a Fluid Custom Property (advanced)

If you need to sync an attribute that isn't in the tables above, Fluid can write it to any person custom property. There is no mapping screen — Fluid matches the SCIM attribute name to the custom property's Key or Label (case-insensitive, ignoring spaces). Deliver it in one of two ways:

  • Inside the enterprise extension block — any attribute whose name matches a custom property Key/Label is picked up automatically; or

  • As a namespaced custom extension — a top-level key that starts with the enterprise URN followed by a dot, e.g. urn:ietf:params:scim:schemas:extension:enterprise:2.0:User.TeamName.

To use this:

  1. Create the person custom property in Fluid.

  2. Map your IdP source attribute to a SCIM attribute whose name exactly matches the property's Key or Label.


Important Notes

  • Exact names matter — a typo in the IdP mapping (e.g. costCentre instead of costCenter) is silently ignored. No error is raised; the field simply won't update.


Was this article helpful?

Sorry about that! Care to tell us more?

Thanks for the feedback!

There was an issue submitting your feedback
Please check your connection and try again.