Stitchflow
Modern Health logo

Modern Health SCIM guide

Connector Only

How to automate Modern Health user provisioning, and what it actually costs

Native SCIM not available

Summary and recommendation

Modern Health, the B2B employee mental health platform, does not support SCIM provisioning on any plan. While Modern Health offers SSO integration with Okta (allowing users to authenticate through their corporate identity provider), this only handles login authentication, not user lifecycle management. IT teams must manually provision and deprovision employee accounts, which is particularly problematic given Modern Health's enterprise-focused pricing model with contracts typically exceeding $100K annually.

This creates a significant operational gap for HR and IT teams managing large employee populations. When employees join, leave, or change roles, administrators must manually update Modern Health access - a time-consuming process that introduces compliance risks around timely deprovisioning of terminated employees from sensitive mental health benefit platforms. The lack of automated provisioning also makes it difficult to maintain accurate employee directory synchronization across the organization's mental health benefits ecosystem.

The strategic alternative

Modern Health 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
OktaOkta SSO integration available. Users can sign in via SSO and are redirected to Okta/SSO login. No SCIM provisioning listed in OIN.
Microsoft Entra IDVia third-partyNo Microsoft Entra gallery provisioning tutorial found.
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 Modern Health 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 Modern Health pricing problem

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

Tier comparison

PlanPriceSSOSCIM
Custom Enterprise~$100k+ annual threshold

Pricing and provisioning matrix

PlanPricingSSOSCIM Provisioning
Custom Enterprise~$100k+ annual threshold✓ Via Okta❌ Not available

Modern Health uses custom enterprise pricing with multi-year agreement preferences. The platform is exclusively B2B focused, requiring significant annual commitments that typically start around $100,000.

What this means in practice

No automated user lifecycle management: IT teams must manually create, update, and deactivate user accounts in Modern Health. When employees join, leave, or change roles, each account requires individual attention.

SSO without provisioning creates gaps: While employees can authenticate through Okta SSO, their Modern Health accounts must still be pre-created manually. This creates a two-step process where SSO handles authentication but provisioning remains manual.

High-value platform with manual overhead: Given Modern Health's significant annual cost (~$100k+), the lack of automated provisioning creates an operational burden that doesn't scale with the platform's enterprise positioning.

Additional constraints

No public API documentation
Modern Health doesn't publish SCIM or user management API documentation
B2B-only focus
Platform designed exclusively for employer-sponsored mental health benefits
Multi-year commitment requirements
Strong preference for long-term contracts increases switching costs
Limited integration ecosystem
Beyond Okta SSO, minimal third-party provisioning options available

Summary of challenges

  • Modern Health 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 Modern Health actually offers for identity

SSO Support (All Plans)

Modern Health provides basic SAML SSO integration through select identity providers:

FeatureSupported?
SAML SSO via Okta✓ Yes
SAML SSO via Entra ID❌ No
OIDC SSO❌ No
User provisioning❌ No
Group synchronization❌ No
Role mapping❌ No

Critical gap: Modern Health's SSO is authentication-only. There's no automated user lifecycle management, meaning you must manually invite each employee to the platform before they can access it via SSO.

No Native SCIM or Provisioning

Modern Health operates as a B2B mental health benefits platform without any automated provisioning capabilities:

No public SCIM API documentation exists
No automated user creation or deactivation
No group or role synchronization
Manual user management required for all employee onboarding/offboarding

The practical impact: HR teams must maintain dual workflows - one in your IdP for authentication and another in Modern Health for user lifecycle management. When employees join or leave, you're updating systems separately, creating compliance gaps and administrative overhead.

Enterprise Pricing Without Enterprise Features

Modern Health's custom enterprise pricing (typically $100k+ annually) includes the same limited identity features as their standard offering. You're paying enterprise rates for manual user management processes that create security and compliance risks at scale.

What IT admins are saying

Modern Health's lack of automated provisioning creates manual overhead for enterprise IT teams managing large employee wellness programs:

  • Manual user account creation required even with SSO configured
  • No SCIM support despite being an enterprise-focused B2B platform
  • Difficult to maintain accurate user lists across large organizations
  • Onboarding/offboarding processes require separate Modern Health admin tasks

Modern Health SSO integration is available through Okta, but provisioning is not supported - accounts still need manual setup.

Okta Integration Network documentation

The recurring theme

Even organizations paying $100k+ annually for Modern Health's enterprise wellness platform must manually manage user accounts. When employees join, leave, or change roles, IT teams can't rely on their identity provider to automatically sync these changes to Modern Health.

The decision

Your SituationRecommendation
Small team (<25 employees) with stable workforceManual management acceptable, use SSO for authentication
Growing company (25-100 employees) with regular hiringUse Stitchflow: manual onboarding becomes time-intensive
Enterprise with high employee turnover or seasonal staffUse Stitchflow: automation essential for HR efficiency
Multi-location deployments with distributed ITUse Stitchflow: centralized provisioning reduces complexity
Organizations with compliance or audit requirementsUse Stitchflow: automated audit trail for access management

The bottom line

Modern Health offers valuable mental health benefits but provides no SCIM provisioning capabilities—even with SSO enabled, user management remains entirely manual. For organizations serious about employee wellbeing automation and identity governance, Stitchflow delivers the provisioning workflow Modern Health should have built natively.

Make Modern Health workflows AI-native

Modern Health 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

B2B employee mental health benefits platformNo public SCIM API documentation foundSSO available but not SCIM provisioningPay-as-you-go or unlimited usage pricing modelsStrong preference for multi-year agreements

Plan requirement

Not specified

Prerequisites

Not specified

Key limitations

  • B2B employee mental health benefits platform
  • No public SCIM API documentation found
  • SSO available but not SCIM provisioning
  • Pay-as-you-go or unlimited usage pricing models
  • Strong preference for multi-year agreements

Documentation not available.

Configuration for Okta

Integration type

Okta Integration Network (OIN) app

Where to enable

Okta Admin Console → Applications → Modern Health → Sign On

Okta SSO integration available. Users can sign in via SSO and are redirected to Okta/SSO login. No SCIM provisioning listed in OIN.

Use Stitchflow for automated provisioning.

Unlock SCIM for
Modern Health

Modern Health 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
Modern Health logo
Modern Health
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