Stitchflow
hireEZ logo

hireEZ SCIM guide

Connector Only

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

Summary and recommendation

HireEZ, the AI-powered talent sourcing platform, does not support SCIM provisioning on any plan, including Enterprise. While hireEZ offers SAML SSO integration with Okta and Microsoft Entra, this only handles authentication - not user lifecycle management. Users must be manually created and activated in hireEZ before they can use SSO, creating a significant operational burden for IT teams managing recruiting software across multiple departments and locations.

This creates a substantial gap for organizations where recruiting teams frequently change - new hires in talent acquisition, departing recruiters, or contractors who need temporary access. Without automated provisioning, IT must manually create each hireEZ account, assign appropriate permissions based on role and team, and remember to deactivate accounts when users leave. Given hireEZ's high per-user pricing (starting at $250/user/month for Professional plans), forgotten active accounts represent both security risks and significant cost leakage.

The strategic alternative

hireEZ 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 only. Supports Group Linking and Schema Discovery. No automated user provisioning - SSO authentication only.
Microsoft Entra IDSSO only. Users must be created manually in hireEZ before using SSO.
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 hireEZ 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 hireEZ pricing problem

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

Tier comparison

PlanPriceSSOSCIM
Starter~$240/month
Professional~$450/month or $5,400/year
EnterpriseCustom quote

Pricing and provisioning features

PlanPricingSSOSCIM
Starter~$240/month❌ Not available❌ Not available
Professional~$450/month or $5,400/year❌ Not available❌ Not available
EnterpriseCustom quote✓ SAML SSO❌ Not available

Key limitation: Even Enterprise customers with SSO enabled cannot automate user provisioning, deprovisioning, or attribute updates.

What this means in practice

IT teams face significant manual overhead:

Initial setup
Every user must be manually created in hireEZ before they can use SSO
Onboarding delays
New hires cannot access hireEZ until someone manually creates their account
Offboarding risk
Departed employees remain active in hireEZ until manually deactivated
Attribute drift
Role changes, department transfers, and other updates require manual synchronization

For a 50-person recruiting team, this creates 15-20 hours of monthly administrative work.

Additional constraints

No API alternative
hireEZ doesn't provide user management APIs that could substitute for SCIM
SSO dependency mismatch
SSO assumes accounts exist, but there's no automated way to create them
Audit complexity
User lifecycle events aren't automatically logged or synchronized with your IdP
Scale limitations
Manual processes become unsustainable as recruiting teams grow

Summary of challenges

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

SAML SSO (Enterprise tier)

hireEZ supports SAML 2.0 integration with identity providers, but with significant manual overhead:

SettingDetails
ProtocolSAML 2.0
Supported IdPsOkta, Microsoft Entra ID
ConfigurationManual SAML setup via Enterprise admin console
User requirementAccounts must exist in hireEZ before SSO login

Critical limitation: Users must be manually created and activated in hireEZ before they can authenticate via SSO. There's no automated account creation or provisioning.

Okta Integration (via OIN)

The official Okta Integration Network listing for hireEZ shows:

FeatureSupported?
SAML SSO✓ Yes
Create users❌ No
Update users❌ No
Deactivate users❌ No
Group push❌ No
Import users❌ No

Microsoft Entra Integration

Microsoft's documentation confirms similar limitations:

FeatureSupported?
SAML SSO✓ Yes
Automatic user provisioning❌ No
User lifecycle management❌ No

What this means: You get authentication through your IdP, but zero automation for user lifecycle management. Every hire, role change, and departure requires manual work in hireEZ.

The Enterprise tier reality

hireEZ Enterprise plans require custom quotes (typically $5,400+ annually per user based on their published Professional tier pricing). The identity features you get:

SAML SSO authentication only
Manual user account creation required
No automated provisioning or deprovisioning
No group-based access management
No automated attribute updates

For teams that just want reliable user provisioning, you're paying Enterprise prices for SSO-only functionality while still managing accounts manually.

What IT admins are saying

hireEZ's lack of automated provisioning creates ongoing friction for IT teams managing recruiting tools:

  • Users must be manually created in hireEZ before SSO authentication works
  • No automated user lifecycle management despite Enterprise pricing
  • IT teams must remember to separately provision/deprovision recruiting team members
  • Manual user management becomes tedious as recruiting teams scale

SSO via SAML only... No automated user provisioning - SSO authentication only.

Okta Integration Network documentation

Users must be created manually in hireEZ before using SSO.

Microsoft Entra documentation

The recurring theme

Even on Enterprise plans costing $250-450/user/month, hireEZ only provides SSO authentication - not provisioning. IT admins must manually create every user account before SSO works, then remember to deactivate accounts when recruiters leave or change roles.

The decision

Your SituationRecommendation
Small recruiting team (<10 users) with stable headcountManual management is workable
Growing talent acquisition team (10-50 users)Use Stitchflow: scaling manual processes becomes costly
Enterprise with multiple recruiting teamsUse Stitchflow: automation essential for consistent access
High-volume recruiting with frequent contractor accessUse Stitchflow: manual onboarding creates bottlenecks
SOX/compliance requirements for user access auditingUse Stitchflow: automated provisioning provides audit trail

The bottom line

hireEZ offers powerful recruiting tools but zero provisioning automation—even their Enterprise SSO requires manual user creation before authentication works. For recruiting teams that need seamless user lifecycle management without the manual overhead, Stitchflow delivers SCIM-level automation that scales with your hiring velocity.

Make hireEZ workflows AI-native

hireEZ 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 supportSSO only via both Okta and Entra - no automated user provisioningUsers must be manually created and activated before SSOFormerly known as Hiretual

Plan requirement

Not specified

Prerequisites

Not specified

Key limitations

  • No native SCIM provisioning support
  • SSO only via both Okta and Entra - no automated user provisioning
  • Users must be manually created and activated before SSO
  • Formerly known as Hiretual

Documentation not available.

Configuration for Okta

Integration type

Okta Integration Network (OIN) app

Where to enable

Okta Admin Console → Applications → hireEZ → Sign On

SSO via SAML only. Supports Group Linking and Schema Discovery. No automated user provisioning - SSO authentication only.

Use Stitchflow for automated provisioning.

Configuration for Entra ID

Integration type

Microsoft Entra Gallery app

Where to enable

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

SSO only. Users must be created manually in hireEZ before using SSO.

Use Stitchflow for automated provisioning.

Unlock SCIM for
hireEZ

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