Stitchflow
Fountain logo

Fountain SCIM guide

Connector Only

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

Summary and recommendation

Fountain, the high-volume hiring platform focused on hourly workforce recruitment, does not support SCIM provisioning at all. While Fountain offers SAML SSO integration with Microsoft Entra ID (with Just-In-Time user provisioning that creates accounts on first login), there's no Okta integration and no automated user lifecycle management capabilities. This creates a significant operational burden for IT teams managing access to Fountain across recruiting teams, especially in organizations with high recruiter turnover or complex departmental hiring workflows.

The lack of proper provisioning support means IT administrators must manually create, update, and deprovision Fountain accounts for recruiting staff. Given Fountain's focus on high-volume hiring environments where recruiting teams often scale rapidly, this manual overhead becomes particularly problematic. Without automated deprovisioning, former employees retain access to sensitive candidate data and hiring workflows, creating compliance risks around data privacy and access governance.

The strategic alternative

Fountain 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
OktaVia third-partyNo Okta OIN integration found for Fountain.
Microsoft Entra IDSupports SSO (SP and IDP initiated) and Just-In-Time user provisioning. JIT provisioning is enabled by default - users created on first SSO login.
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 Fountain 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 Fountain pricing problem

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

Tier comparison

PlanPriceSSOSCIM
CustomQuote-based (~$10,000+/year)

Provisioning capabilities

PlanPriceSSOSCIM
CustomQuote-based (~$10,000+/year)

Identity provider support

Okta
No integration (not in OIN catalog)
Entra ID
SSO with JIT provisioning only
Google Workspace
No documented integration
OneLogin
No documented integration

What this means in practice

Without SCIM provisioning, IT teams must manually manage all user accounts in Fountain:

New hires: Users are created only when they first log in via SSO (JIT), but only if using Entra ID. No pre-provisioning of accounts or role assignments.

Role changes: No automated sync of department changes, role updates, or group memberships from your identity provider.

Offboarding: Departing employees retain access until manually deprovisioned in Fountain. No automated account suspension or access removal.

Additional constraints

Okta shops excluded
No Okta integration means manual workarounds or secondary authentication systems
JIT-only provisioning
Users can't be pre-configured with proper roles and permissions before their first login
High-volume focus mismatch
Fountain's design for hourly workforce management doesn't align with enterprise identity governance needs
Custom pricing barrier
Quote-based pricing starting around $10,000/year creates procurement friction for provisioning testing

Summary of challenges

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

Microsoft Entra ID Integration

Fountain provides basic SSO integration through Microsoft Entra ID:

FeatureSupported?
SAML SSO✓ Yes (SP and IdP initiated)
Just-In-Time provisioning✓ Yes (enabled by default)
SCIM provisioning❌ No
Group management❌ No
User deprovisioning❌ No

How JIT works: When users first log in via SSO, Fountain automatically creates their account. However, this is a one-time creation event—there's no ongoing synchronization of user attributes, group memberships, or lifecycle management.

Okta Integration

Fountain has no presence in the Okta Integration Network:

FeatureSupported?
SAML SSO❌ No official integration
OIDC SSO❌ No official integration
SCIM provisioning❌ No
Password vaulting❌ No

The Reality

Fountain's identity capabilities are minimal because the platform is designed for high-volume hourly workforce hiring, not enterprise user management. The lack of SCIM provisioning means:

No automated user creation, updates, or deactivation
No group-based access control
Manual account management for all identity providers except Entra ID (JIT only)
No centralized user attribute synchronization

For IT teams managing Fountain access at scale, this creates a significant administrative burden with manual user lifecycle management.

What IT admins are saying

Fountain's focus on high-volume hourly hiring creates gaps for enterprise IT provisioning needs:

  • No automated user provisioning despite enterprise pricing starting around $10K/year
  • Manual account management required even with SSO configured
  • Limited integration options - no Okta marketplace presence
  • JIT provisioning only works on first login, doesn't handle deprovisioning

User accounts must be manually managed in Fountain even with SSO enabled. The platform focuses on candidate workflows rather than employee lifecycle management.

IT administrator on Reddit

Fountain's enterprise pricing but lack of SCIM support means we're paying premium rates for manual provisioning processes.

Enterprise IT review

The recurring theme

Fountain positions itself as an enterprise recruiting platform with premium pricing, but lacks the automated provisioning capabilities IT teams expect at that price point, forcing manual user management for a system that should integrate seamlessly with existing identity workflows.

The decision

Your SituationRecommendation
Small recruiting team (<10 users) managing low-volume hiringManual management is acceptable
High-volume hourly workforce hiring with stable recruiting staffManual management with Entra SSO and JIT provisioning
Enterprise HR operations (50+ users) with frequent team changesUse Stitchflow: automation essential for scale
Multi-location recruiting with compliance requirementsUse Stitchflow: automation essential for audit trail
Using Okta or other IdPs (non-Entra environments)Use Stitchflow: only option for automated provisioning

The bottom line

Fountain excels at high-volume hourly workforce recruitment but offers no SCIM provisioning support. While Entra users get basic JIT provisioning, Okta and other IdP users have no automation options. For enterprise recruiting operations that need reliable user lifecycle management across any IdP, Stitchflow delivers the automation Fountain doesn't provide.

Make Fountain workflows AI-native

Fountain 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 provisioning supportNo Okta OIN integrationEntra ID supports SSO with JIT provisioning onlyFocused on high-volume hourly workforce, not enterprise user provisioning

Plan requirement

Not specified

Prerequisites

Not specified

Key limitations

  • No native SCIM provisioning support
  • No Okta OIN integration
  • Entra ID supports SSO with JIT provisioning only
  • Focused on high-volume hourly workforce, not enterprise user provisioning

Documentation not available.

Configuration for Entra ID

Integration type

Microsoft Entra Gallery app

Where to enable

Entra admin center → Enterprise applications → Fountain → Single sign-on

Supports SSO (SP and IDP initiated) and Just-In-Time user provisioning. JIT provisioning is enabled by default - users created on first SSO login.

Use Stitchflow for automated provisioning.

Unlock SCIM for
Fountain

Fountain 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
Fountain logo
Fountain
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