Early Access Feature

User Attribute Sync via SCIM

Sync job title, practice area, and more from your identity provider directly into Harvey, keeping profiles accurate and powering richer insights in Command Center.

Timeline
September 9 (General Availability)
Categories
Governance
General Availability Access
Regional Availability
US, EU, AU

Interested in testing this feature?

Contact your Customer Success Manager for early access.


Overview

Harvey now accepts additional standard SCIM attributes from Entra ID and Okta and maps them directly to profile fields. When your IT team provisions or updates a user in your identity provider (IdP), their Harvey profile updates automatically, matching your firm's taxonomy.

Harvey maps the following standard attributes:

Identity Provider Attribute

Harvey Attribute

Name (givenName + familyName)

Full name

Title

Job title

Department

Practice area

Division

Primary profession

Address fields

Country and Primary work location

Admins can also configure custom attribute mappings, pointing a firm-specific SCIM attribute (such as a custom practice group taxonomy) at a supported Harvey field instead of using the default mapping.

Once a field syncs from your identity provider, it's locked in Harvey, so no one can accidentally overwrite it by editing their profile directly. Your identity provider stays the single, trusted source for that data.

How to Use

If your workspace already has SCIM set up through Entra ID or Okta, the additional attributes will sync automatically after an admin has configured attribute mapping. The new data flows in the next time a profile is created or updated.

You can find more information on configuring SCIM in your workspace in our SCIM (System for Cross-domain Identity Management) Integration article.

FAQs

Q: Can firms use their own practice group taxonomy instead of Harvey's defaults?

Yes. Admins can configure custom attribute mappings to point a firm-specific SCIM attribute at a supported Harvey field, instead of relying on the default mapping.

Q: What happens to fields that aren't synced via SCIM?

Fields not sent by the identity provider remain user-editable. For multi-select fields like practice area, users can still add non-synced values alongside any SCIM-synced ones.

Q: How does these additional mappings impact the product experience?

This ensures reporting data and analytics are reliable in areas like the Command Center, allowing you to make better data-driven decisions and generate accurate reports and presentations.