Stitchflow
PartnerStack logo

PartnerStack SCIM guide

Connector Only

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

Summary and recommendation

PartnerStack, the partner relationship management platform, offers no SCIM provisioning support across any of its custom-priced plans. The platform operates with two distinct user types—company teammates and external partners—but lacks any automated user lifecycle management through identity providers. While PartnerStack supports SAML SSO for company teammates and Google OAuth for authentication, these only handle login credentials, not account creation, role assignment, or deprovisioning. IT teams must manually create and manage all user accounts directly in PartnerStack's interface.

This creates a significant operational burden for organizations managing both internal teams and external partner ecosystems. Without automated provisioning, IT admins face manual overhead for every partner onboarding, role change, and offboarding event. The dual user type architecture compounds this complexity—internal employees need different access patterns than external partners, but both require manual intervention. For companies with extensive partner networks, this translates to hours of repetitive administrative work and increased security risk from delayed deprovisioning.

The strategic alternative

PartnerStack 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 available.
Microsoft Entra IDVia third-partyNo Entra gallery integration.
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 PartnerStack 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 PartnerStack pricing problem

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

Tier comparison

PlanPriceSSOSCIM
ProCustom quote
BusinessCustom quote
EnterpriseCustom quote (+ 3-15% commission)

Pricing and provisioning availability

PlanPricingSCIMSSO
ProCustom quote❌ Not available❌ Not available
BusinessCustom quote❌ Not available❌ Not available
EnterpriseCustom quote (+ 3-15% commission)❌ Not available⚠️ Company users only

What this means in practice

Without SCIM support, IT teams must handle all PartnerStack user lifecycle management manually:

No automated provisioning
Users must be created manually in PartnerStack
No role synchronization
Job title changes don't automatically update PartnerStack permissions
No deprovisioning
Terminated employees remain active until manually removed
Dual user complexity
PartnerStack has two distinct user types (company teammates vs. external partners), each requiring different management approaches

Even at the Enterprise level, SAML SSO only works for internal company users - not for external partners who use the platform.

Additional constraints

No public pricing
All plans require custom quotes, making budget planning difficult
Commission-based costs
Enterprise plans include 3-15% commission fees on top of base pricing
Limited authentication options
Partners rely on Google OAuth, creating security gaps
No IdP integration
Missing from Okta OIN and Entra galleries entirely
Partner access complexity
External partners can't benefit from your organization's SSO infrastructure

Summary of challenges

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

Limited Identity Features (Custom Plans Only)

PartnerStack offers minimal identity management capabilities, focused primarily on their dual-user model (company teammates vs. external partners):

FeatureAvailability
SAML SSOCompany teammates only
Google OAuth✓ Available
SCIM provisioning❌ Not supported
IdP integrations❌ None available
Automated user management❌ Not supported

Key limitations for IT teams:

SAML SSO works only for internal company users, not partner users
No Okta OIN or Entra gallery integrations available
Zero provisioning capabilities all user management is manual
Custom pricing model makes budgeting unpredictable (3-15% commission fees)

Why This Falls Short

PartnerStack's identity approach creates operational friction:

Dual identity systems
Internal users get SAML, partners use separate authentication
Manual user lifecycle
No automated provisioning, deprovisioning, or attribute updates
No centralized control
Partners manage their own access outside your IdP
Compliance gaps
Limited audit trails and access governance for partner relationships

The platform essentially requires you to manage two separate identity paradigms - one for employees and another for external partners - without the automation tools enterprises expect.

What IT admins are saying

PartnerStack's absence of automated provisioning creates operational headaches for IT teams managing both company teammates and external partners:

  • Manual account creation required for all users despite SAML SSO availability
  • No IdP integration means separate user lifecycle management
  • Partner onboarding becomes an IT bottleneck when accounts must be provisioned individually
  • Dual user types (company teammates vs. partners) complicate access management workflows

SAML SSO is available for company teammates only, not for partners using the platform.

PartnerStack support documentation

All user accounts require manual provisioning - there's no automated sync with identity providers.

IT admin on Reddit

The recurring theme

PartnerStack forces IT teams to manage user provisioning entirely outside their identity provider workflow, creating manual overhead for both internal teammates and external partner access - exactly when organizations need streamlined partner onboarding the most.

The decision

Your SituationRecommendation
Small partner program (<20 company users)Manual management acceptable for internal team only
Partner-heavy program with frequent onboardingUse Stitchflow: dual user types require automation
Enterprise with compliance requirementsUse Stitchflow: audit trail essential for partner access
Growing SaaS with scaling partner ecosystemUse Stitchflow: manual management becomes bottleneck
Multi-tier partner programs with complex accessUse Stitchflow: automation critical for role management

The bottom line

PartnerStack lacks any native SCIM support and offers limited SSO only for company teammates—not partners. With dual user types and custom-only pricing, manual provisioning becomes a scaling nightmare. For partner programs that need proper identity governance, Stitchflow delivers the automation that PartnerStack doesn't provide.

Make PartnerStack workflows AI-native

PartnerStack 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 supportSAML SSO available for company teammates only (not partners)No IdP gallery integrationsPartner management platform with dual user types (company/partners)Custom pricing only - no public tiersSupports Google OAuth for authentication

Plan requirement

Not specified

Prerequisites

Not specified

Key limitations

  • No native SCIM support
  • SAML SSO available for company teammates only (not partners)
  • No IdP gallery integrations
  • Partner management platform with dual user types (company/partners)
  • Custom pricing only - no public tiers
  • Supports Google OAuth for authentication

Documentation not available.

Unlock SCIM for
PartnerStack

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