Stitchflow
Crisp logo

Crisp SCIM guide

Connector Only

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

Summary and recommendation

Crisp, the customer messaging platform used for live chat and support automation, does not support SCIM provisioning on any plan. In fact, Crisp doesn't even document enterprise SSO capabilities—their security documentation only mentions 2FA via Google Authenticator or SMS. This creates a significant gap for IT teams managing support agents across multiple workspaces, especially since Crisp uses workspace-based pricing rather than per-agent billing.

The lack of automated provisioning means IT admins must manually create, update, and deactivate accounts for support agents as team composition changes. For growing support teams that need access to multiple customer workspaces, this manual process becomes error-prone and time-consuming. Without SSO integration, password policies and access controls remain fragmented outside your central identity management system.

The strategic alternative

Crisp 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 protocolNot documented
DocumentationNot available

Supported identity providers

IdPSSOSCIMNotes
OktaVia third-partyNo Okta integration. No enterprise SSO features documented.
Microsoft Entra IDVia third-partyNo Entra ID integration. 2FA available via Google Authenticator or SMS only.
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 Crisp accounts manually. Here's what that costs:

Source: Stitchflow aggregate data across apps with 2+ instances, normalized to 500 employees
Orphaned accounts (ex-employees with access)7
Unused licenses12
IT hours spent on manual management/year101 hours
Unused license cost/year$3,925
IT labor cost/year$6,088
Cost of compliance misses/year$1,741
Total annual financial impact$11,754

The Crisp pricing problem

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

Tier comparison

PlanPriceSSOSCIM
Free€0/month
Mini€45/month
Essentials€95/month
Plus€295/month

Pricing structure

PlanPriceSSOSCIM
Free€0/month
Mini€45/month
Essentials€95/month
Plus€295/month

What this means in practice

Without SCIM or SSO, IT administrators must:

Manually create and delete user accounts for support agents
Rely on username/password authentication with basic 2FA
Handle workspace access permissions through Crisp's native interface
Manage user lifecycle events (role changes, departures) outside their identity provider

For support teams that scale rapidly or have frequent staffing changes, this creates significant administrative overhead.

Additional constraints

No enterprise authentication
No SAML, OIDC, or directory integration documented
Workspace-based pricing
€295/month per workspace regardless of agent count (additional agents cost €10 each)
Basic security only
Limited to SMS or authenticator app 2FA
Manual onboarding
New support agents require individual account setup and training on Crisp's access controls

Summary of challenges

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

No Enterprise Identity Management

Crisp's customer messaging platform focuses on workspace-based communication but lacks enterprise identity features:

FeatureSupported?
SAML SSO❌ No
OIDC SSO❌ No
SCIM provisioning❌ No
Directory sync❌ No
JIT provisioning❌ No

Available Security Features

What Crisp does offer for account security:

Two-Factor Authentication
Google Authenticator or SMS-based 2FA
Basic user management
Manual agent invitations within workspaces
Role-based permissions
Support agent, admin, and owner roles per workspace

The Enterprise Gap

For organizations running customer support teams, Crisp's lack of SSO creates several operational challenges:

Manual onboarding
Every support agent must be invited individually to each workspace
No centralized deprovisioning
Former employees retain access until manually removed
Audit trail gaps
No integration with corporate identity systems for compliance reporting
Multi-workspace complexity
Teams using multiple Crisp workspaces face exponential management overhead

The €295/month Plus plan includes advanced analytics and integrations, but none of these enterprise features address identity management. Organizations needing federated authentication must contact Crisp directly to explore custom enterprise options not publicly documented.

What IT admins are saying

Crisp's lack of enterprise authentication creates headaches for IT teams managing customer support operations:

  • No SSO integration means manual password management for all support agents
  • No SCIM provisioning requires manual user lifecycle management across workspaces
  • 2FA limited to Google Authenticator or SMS - no enterprise-grade authentication options
  • Multi-workspace environments need separate user management for each workspace

No enterprise SSO options documented

IT admin feedback on Crisp's authentication capabilities

Customer messaging platform. 2FA available. SSO/SCIM not documented.

Technical assessment of Crisp's enterprise readiness

The recurring theme

Support teams using Crisp operate in an identity management vacuum. Every agent onboarding, offboarding, and workspace access change requires manual intervention, creating security risks and administrative overhead that scales poorly with team growth.

The decision

Your SituationRecommendation
Small support team (<10 agents, single workspace)Manual management is acceptable
Growing customer success team with occasional turnoverUse Stitchflow: workspace management gets complex quickly
Multi-workspace deployment (different brands/regions)Use Stitchflow: essential for cross-workspace provisioning
Enterprise with compliance requirementsUse Stitchflow: no native SSO or audit capabilities
Integration with existing identity workflowsUse Stitchflow: Crisp offers no enterprise identity features

The bottom line

Crisp provides solid customer messaging capabilities with workspace-based pricing, but completely lacks enterprise identity management features—no documented SSO, no SCIM, just basic 2FA. For organizations that need automated provisioning across Crisp workspaces, Stitchflow provides the missing identity layer that Crisp doesn't offer.

Make Crisp workflows AI-native

Crisp 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

SCIM provisioning not availableSSO not publicly documented2FA via Google Authenticator or SMS

Plan requirement

Not specified

Prerequisites

Not specified

Key limitations

  • SCIM provisioning not available
  • SSO not publicly documented
  • 2FA via Google Authenticator or SMS

Documentation not available.

Unlock SCIM for
Crisp

Crisp 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
Crisp logo
Crisp
via Stitchflow

Last updated: 2026-01-11

* Pricing and features sourced from public documentation.

Keep exploring

Related apps

Freshchat logo

Freshchat

No SCIM

Customer Messaging / Live Chat

ProvisioningNot Supported
Manual Cost$11,754/yr

Freshchat offers SCIM provisioning only on Enterprise plans ($95/agent/month), but only through specific marketplace apps for OneLogin and Azure AD - not as native SCIM functionality. This creates a significant limitation for organizations using other identity providers like Okta or Google Workspace, who must rely on workarounds or manual provisioning. Even with supported IdPs, the implementation requires installing separate Freshworks marketplace apps rather than standard SCIM connectors, adding complexity to your identity management stack. The restricted SCIM support creates operational friction for IT teams managing Freshchat access across support, sales, and customer success teams. Without proper provisioning automation, organizations face the dual burden of manual user lifecycle management and the security risk of orphaned accounts when agents leave or change roles. For growing support teams that need rapid onboarding and consistent access controls, the Enterprise-only requirement represents a substantial cost barrier - potentially adding tens of thousands annually just to access basic provisioning capabilities.

View full guide
6sense logo

6sense

No SCIM

B2B Revenue Intelligence / ABM

ProvisioningNot Supported
Manual Cost$11,754/yr

6sense, the B2B revenue intelligence platform, has paused SCIM provisioning for new customers until Q4 2026. While existing customers with SCIM enabled can continue using it, new implementations are limited to JIT (Just-In-Time) provisioning through SAML SSO. This creates a significant gap for IT teams managing revenue intelligence access, as JIT only creates users on first login and provides minimal attribute mapping (email, first name, last name only). For an enterprise platform with typical pricing of $55,000-$130,000 annually, the absence of automated user lifecycle management is a substantial limitation. The lack of SCIM until Q4 2026 forces IT teams into manual provisioning workflows for a platform handling sensitive revenue data. While SAML SSO handles authentication, it doesn't address user lifecycle events like role changes, department transfers, or offboarding. This creates compliance risks in revenue teams where access to prospect data and sales intelligence must be tightly controlled. The nearly two-year wait for SCIM restoration means organizations implementing 6sense today face manual user management for the foreseeable future.

View full guide
ActiveCampaign logo

ActiveCampaign

No SCIM

Marketing Automation / Email

ProvisioningNot Supported
Manual Cost$11,754/yr

ActiveCampaign, the marketing automation platform, does not offer native SCIM provisioning on any plan. While the Enterprise plan ($145+/month) includes SAML 2.0 SSO with just-in-time (JIT) provisioning, this only creates user accounts on first login—there's no automated deprovisioning when employees leave or change roles. New SSO users are automatically added to a generic "SSO Users" group with configurable permissions, but IT teams have no way to programmatically manage user lifecycles or enforce granular access controls based on department or role changes. This creates a significant gap for marketing teams that need to manage access to customer data and campaign tools. When employees leave the company or change departments, their ActiveCampaign access must be manually revoked, creating compliance risks and potential data exposure. The lack of automated deprovisioning means former employees could theoretically retain access to sensitive marketing data and customer information until someone manually removes them from the platform.

View full guide