Stitchflow
Relativity logo

Relativity SCIM guide

Connector Only

How to automate Relativity user provisioning, and what it actually costs

Native SCIM not available

Summary and recommendation

Relativity, the enterprise eDiscovery platform used by law firms and corporate legal departments, does not support native SCIM provisioning on any plan. While Relativity integrates with identity providers like Okta and Entra ID for SAML 2.0 SSO, user provisioning relies entirely on Just-in-Time (JIT) provisioning. This creates a significant operational gap: JIT only creates user accounts on first authentication and cannot update user attributes, assign proper permissions, or handle deprovisioning when employees leave or change roles.

For legal organizations managing sensitive case data and strict compliance requirements, this limitation creates serious security risks. Users retain access until manually deprovisioned, and there's no automated way to update user attributes or group memberships as organizational roles change. The lack of proper lifecycle management is particularly problematic given Relativity's usage-based pricing model—orphaned accounts continue accruing costs while potentially exposing confidential legal data.

The strategic alternative

Relativity has no native SCIM. Automate offboarding, user access reviews, and license workflows across every app, including the ones without APIs. We maintain the integration layer underneath. You focus on judgment, not plumbing.

Quick SCIM facts

SCIM available?No
SCIM tier requiredN/A
SSO required first?No
SSO available?Yes
SSO protocolSAML 2.0
DocumentationNot available

Supported identity providers

IdPSSOSCIMNotes
OktaSSO via SAML 2.0 and OpenID Connect. Group Linking and Schema Discovery available but no SCIM user provisioning.
Microsoft Entra IDSSO via SAML 2.0 or OpenID Connect. JIT provisioning supported.
Google WorkspaceVia third-partyNo native support
OneLoginVia third-partyNo native support

The cost of not automating

Without SCIM (or an alternative like Stitchflow), your IT team manages Relativity accounts manually. Here's what that costs:

Source: Stitchflow research, normalized to 500 employees:
Orphaned accounts (ex-employees with access)5
Unused licenses12
IT hours spent on manual management/year85 hours
Unused license cost/year$3,500
IT labor cost/year$5,100
Cost of compliance misses/year$890
Total annual financial impact$9,490

The Relativity pricing problem

Relativity gates SCIM provisioning behind premium plans, forcing significant cost increases for basic user management.

Tier comparison

PlanPriceSSOSCIM
RelativityOneCustom (usage-based, per-GB)

Pricing and provisioning options

PlanPricingSCIMSSO
RelativityOneCustom (usage-based, per-GB)❌ Not available✓ SAML 2.0/OIDC

Pricing context

Usage-based model with volume discounts up to 50%
Costs scale with data volume (per-GB storage and processing)
RelativityOne Connect required for multi-instance SSO deployments

What this means in practice

JIT provisioning limitations

Users only created on first successful authentication
No automatic attribute updates after initial account creation
No user deprovisioning when accounts are disabled in your IdP
Group memberships and permissions require manual configuration

Real-world scenario: When a legal team member leaves, their Relativity access remains active even after you disable their corporate account. IT must manually track and remove these orphaned accounts across potentially multiple Relativity instances.

Additional constraints

Separate user stores
RelativityOne and Relativity Server maintain independent user databases, requiring duplicate management effort
Multi-instance complexity
Large legal organizations often run multiple Relativity instances, each requiring separate user management
Volume-based costs
Usage pricing means provisioning inefficiencies directly impact your bill through wasted storage and processing capacity
Compliance gaps
Manual deprovisioning creates audit trail gaps for organizations with strict data access requirements

Summary of challenges

  • Relativity does not provide native SCIM at any price tier
  • Organizations must rely on third-party tools or manual provisioning
  • Our research shows teams manually provisioning this app spend significant hidden costs annually

What Relativity actually offers for identity

SAML SSO (Standard)

Relativity supports federated authentication through multiple protocols:

ProtocolSupported
SAML 2.0✓ Yes
OpenID Connect✓ Yes
JIT provisioning✓ Yes (basic)
User attribute updates❌ No

Critical limitation: JIT provisioning only creates users on first login. Once created, user attributes (email, role assignments, group memberships) are never updated automatically, even if they change in your IdP.

Okta Integration (via OIN)

The official Okta Integration Network listing for Relativity shows:

FeatureSupported?
SAML SSO✓ Yes
OIDC SSO✓ Yes
Create users✓ Yes (JIT only)
Update users❌ No
Deactivate users❌ No
Group push❌ No
SCIM provisioning❌ No

Additional complexity: RelativityOne and Relativity Server maintain separate user stores. Multi-instance SSO requires RelativityOne Connect licensing.

Microsoft Entra Integration

Entra ID supports SAML 2.0 and OpenID Connect for Relativity with the same JIT limitations:

Users created on first authentication only
No ongoing synchronization of user attributes
No automated deprovisioning when users are removed from Entra ID
Manual user management required for role changes

The core problem: Relativity's JIT approach creates a one-time snapshot of user data. Any subsequent changes in your identity provider (role updates, group changes, user deactivation) never sync to Relativity, forcing manual administration.

What IT admins are saying

Relativity's reliance on JIT provisioning instead of proper SCIM creates ongoing headaches for IT teams managing eDiscovery access:

  • Users must authenticate before their accounts are created, causing confusion during onboarding
  • User attributes never update after initial JIT creation - outdated department, role, and contact information persist indefinitely
  • No way to pre-provision accounts or bulk manage user lifecycle changes
  • Complex pricing model makes it difficult to predict costs when adding users at scale

JIT provisioning supported

Microsoft Entra documentation on Relativity integration

Group Linking and Schema Discovery available but no SCIM user provisioning

Okta Integration Network listing

The recurring theme

IT teams are stuck with a "set it and forget it" approach that works poorly in practice. Once users are created via JIT, there's no automated way to keep their information current or manage their lifecycle, forcing manual intervention for any user management beyond initial login.

The decision

Your SituationRecommendation
Small legal team (<20 users, minimal case volume)Manual management is acceptable
Established firm with stable paralegal/attorney rosterManual management with SSO for authentication
Large law firm or corporate legal department (50+ users)Use Stitchflow: automation essential for case staffing
Multi-matter environment with frequent user role changesUse Stitchflow: automation essential for access control
eDiscovery service provider with client-based provisioningUse Stitchflow: automation strongly recommended

The bottom line

Relativity is the industry standard for eDiscovery, but it offers only JIT provisioning—users are created once on first login, then never updated. For legal teams managing complex case access and evolving user roles across matters, Stitchflow delivers the SCIM-level automation that Relativity doesn't provide.

Make Relativity workflows AI-native

Relativity has no native SCIM. We build complete offboarding, user access reviews, and license workflows across every app, including the ones without APIs.

Covers apps without native SCIM, including the ones without APIs
Less than a week, start to finish (~2 hours of your time)
Built with your team; extend to anything else in the company
Book a Demo

Technical specifications

SCIM Version

Not specified

Supported Operations

Not specified

Supported Attributes

No native SCIM endpoint - uses JIT provisioning insteadJIT provisioning creates users on first authentication onlyUser attributes not automatically updated after initial creationSeparate user stores between Relativity Server and RelativityOneUsage-based pricing with volume discounts up to 50%Requires RelativityOne Connect for multi-instance SSO

Plan requirement

Not specified

Prerequisites

Not specified

Key limitations

  • No native SCIM endpoint - uses JIT provisioning instead
  • JIT provisioning creates users on first authentication only
  • User attributes not automatically updated after initial creation
  • Separate user stores between Relativity Server and RelativityOne
  • Usage-based pricing with volume discounts up to 50%
  • Requires RelativityOne Connect for multi-instance SSO

Documentation not available.

Configuration for Okta

Integration type

Okta Integration Network (OIN) app

Where to enable

Okta Admin Console → Applications → Relativity → Sign On

SSO via SAML 2.0 and OpenID Connect. Group Linking and Schema Discovery available but no SCIM user provisioning.

Use Stitchflow for automated provisioning.

Unlock SCIM for
Relativity

Relativity has no native SCIM. We still automate end-to-end workflows across every app, including the ones without APIs.

See how it works
Admin Console
Directory
Applications
Relativity logo
Relativity
via Stitchflow

Last updated: 2026-01-20

* Pricing and features sourced from public documentation.

Keep exploring

Related apps

Abnormal Security logo

Abnormal Security

No SCIM

Security / Email Security

ProvisioningNot Supported
Manual Cost$9,490/yr

Abnormal Security, the AI-powered email security platform protecting against BEC and phishing attacks, does not offer SCIM provisioning on any plan. While the platform supports SAML 2.0 SSO integration with identity providers like Okta and Entra ID, this only handles authentication—not automated user lifecycle management. Security teams must manually provision and deprovision analyst access through Abnormal's portal, creating operational overhead and potential security gaps in a platform specifically designed to protect against email-based threats. This manual provisioning model creates significant challenges for security operations. When new SOC analysts join or existing team members change roles, IT admins must coordinate manual account creation and permission updates in Abnormal Security. For a platform that's critical to threat detection and incident response, delays in provisioning can leave security gaps, while delayed deprovisioning creates compliance risks. The irony is stark: a security platform designed to prevent account takeover and credential abuse lacks the automated provisioning controls that prevent exactly these risks.

View full guide
Airwallex logo

Airwallex

No SCIM
ProvisioningNot Supported
Manual Cost$9,490/yr

Airwallex, the global payments and treasury platform, offers no SCIM provisioning support on any plan, including their custom Accelerate enterprise tier. Despite being positioned for enterprise use with features like multi-entity management and advanced treasury controls, Airwallex lacks any official identity provider integrations—no SSO, no provisioning, and no presence in major IdP galleries like Okta's OIN or Microsoft Entra. This creates a significant operational burden for IT teams managing financial access across growing organizations, where manual user provisioning and deprovisioning in a payments platform presents both efficiency and security risks. The absence of identity management capabilities means IT administrators must manually create, update, and remove user accounts in Airwallex—a particularly concerning gap given that this platform handles sensitive financial operations, cross-border payments, and treasury management. Without automated deprovisioning, former employees could retain access to financial systems, creating compliance risks and potential security vulnerabilities that most finance and IT teams cannot afford to overlook.

View full guide
Alkami logo

Alkami

No SCIM
ProvisioningNot Supported
Manual Cost$9,490/yr

Alkami, the digital banking platform used by banks and credit unions, does not offer SCIM provisioning or public SSO integrations. As an enterprise-only platform with custom pricing, Alkami appears to handle user management through direct account administration rather than standardized identity protocols. This creates significant challenges for financial institutions that need to integrate Alkami with their existing identity infrastructure—particularly problematic given the compliance requirements and security standards that banks must maintain. The lack of automated provisioning means IT teams at financial institutions must manually create, update, and deprovision user accounts in Alkami. For a platform handling sensitive financial data and customer information, this manual approach introduces compliance risks and operational overhead. Banks typically require seamless integration between their core identity systems and all applications accessing customer data.

View full guide