Stitchflow
Lifesize logo

Lifesize SCIM guide

Connector Only

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

Summary and recommendation

Lifesize, the video conferencing platform now owned by Enghouse, does not offer SCIM provisioning on any plan. While Lifesize supports SAML 2.0 SSO integration with identity providers like Okta, Azure AD, and generic SAML providers, this only handles authentication—not user lifecycle management. IT teams must manually create, update, and deactivate user accounts in the Lifesize admin console, even though SSO can authenticate users once they exist in the system.

This creates a significant operational gap for organizations using Lifesize for company-wide video conferencing. Without automated provisioning, IT teams face the ongoing burden of manually managing user accounts as employees join, change roles, or leave the organization. For video conferencing platforms where user access needs to scale with organizational changes, this manual overhead becomes particularly problematic during onboarding/offboarding cycles and can create security risks when former employees retain access to meeting capabilities.

The strategic alternative

Lifesize 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-partySupports SAML and SWA. User creation on assignment. Configure SSO in Lifesize Cloud Advanced Settings. Attribute mapping: firstname, lastname, email.
Microsoft Entra IDVia third-partySP initiated SSO. Supports automated user provisioning. Available in Microsoft Entra US Government Cloud. Configure in Lifesize Cloud Advanced Settings.
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 Lifesize 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 Lifesize pricing problem

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

Tier comparison

PlanPriceSSOSCIM
Free$0 (25 participants)
Standard$16.95/host/month
Plus$14.95/host/month (15+ hosts)
Enterprise$12.95/host/month (50+ hosts)

Pricing structure

PlanPriceSSOSCIM
Free$0 (25 participants)
Standard$16.95/host/month
Plus$14.95/host/month (15+ hosts)
Enterprise$12.95/host/month (50+ hosts)

What this means in practice

Without SCIM, IT teams must manually:

Create user accounts before employees can access video conferencing
Update user information when roles or departments change
Remove access when employees leave (critical for security)
Manage host licenses and meeting permissions individually

For a 200-person company on the Enterprise plan ($2,590/month), this manual overhead becomes significant. New hires can't immediately join video calls, and offboarding delays create security risks with former employees potentially retaining meeting host privileges.

Additional constraints

IdP limitations
Only supports Okta, Azure AD, and generic SAML - no Google Workspace or OneLogin integration
No just-in-time provisioning
Users must be manually created in Lifesize before SSO works
Acquisition uncertainty
Recent Enghouse acquisition may impact future development priorities
Manual license management
Host permissions require individual assignment, complicating bulk user operations

Summary of challenges

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

SAML SSO (Enterprise tier)

Lifesize supports SAML 2.0 single sign-on with select identity providers:

SettingDetails
ProtocolSAML 2.0
Supported IdPsOkta, Azure AD/Entra, generic SAML providers
ConfigurationConfigure in Lifesize Cloud Advanced Settings
User provisioningManual only - no SCIM support

The reality: While Lifesize offers SAML SSO, there's no documented SCIM provisioning capability. Users must be manually created in Lifesize before they can authenticate via SSO.

Identity Provider Integrations

IdPSSO SupportProvisioning Method
Okta✓ SAML/SWAUser creation on assignment only
Azure AD/Entra✓ SAML"Automated provisioning" (unclear method)
Google Workspace❌ NoManual only
OneLogin❌ NoManual only

Translation: Despite Microsoft's documentation claiming "automated user provisioning" for Azure AD, Lifesize has no published SCIM endpoints. The Okta integration supports basic user creation on assignment, but lacks true lifecycle management (updates, deprovisioning, group sync).

What's actually missing

No SCIM API
No standardized provisioning protocol
Limited IdP support
Only Okta and Azure AD have any form of automated user creation
No deprovisioning
Users remain active when removed from IdP groups
No attribute sync
Profile updates don't flow from IdP to Lifesize
No group management
Team assignments must be managed manually

For a video conferencing platform where meeting access needs change frequently, the lack of proper provisioning creates ongoing administrative overhead.

What IT admins are saying

Community sentiment on Lifesize's provisioning capabilities reflects the reality of managing video conferencing without SCIM automation:

  • Manual user provisioning required despite SSO availability
  • No documented SCIM endpoint for automated lifecycle management
  • Reliance on individual account creation for each meeting host
  • Acquisition by Enghouse has left uncertainty about future automation features

"User creation on assignment" sounds automated, but IT admins quickly discover this only works during the initial SSO handoff - ongoing management still requires manual intervention.

The recurring theme

While Lifesize supports SAML SSO through major identity providers, the absence of SCIM means IT teams must manually provision and deprovision meeting hosts, creating administrative overhead that scales poorly as organizations grow.

The decision

Your SituationRecommendation
Small video conferencing team (<25 users)Manual management is acceptable given no SCIM option
Medium organization using Free/Standard plansManual provisioning with SAML SSO for authentication
Enterprise deployment (50+ hosts)Use Stitchflow: automation essential for scale
Multi-location company with frequent joiners/leaversUse Stitchflow: manual provisioning becomes unmanageable
Organizations requiring audit trails for complianceUse Stitchflow: automated provisioning provides necessary documentation

The bottom line

Lifesize offers solid video conferencing capabilities with SAML SSO, but provides no SCIM support for automated user provisioning. For organizations managing more than a handful of hosts, manual user creation becomes a bottleneck that Stitchflow eliminates entirely.

Make Lifesize workflows AI-native

Lifesize 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 documented SCIM supportSAML 2.0 SSO availableAzure integration documented

Plan requirement

Not specified

Prerequisites

Not specified

Key limitations

  • No documented SCIM support
  • SAML 2.0 SSO available
  • Azure integration documented

Documentation not available.

Configuration for Okta

Integration type

Okta Integration Network (OIN) app

Where to enable

Okta Admin Console → Applications → Lifesize → Sign On

Supports SAML and SWA. User creation on assignment. Configure SSO in Lifesize Cloud Advanced Settings. Attribute mapping: firstname, lastname, email.

Use Stitchflow for automated provisioning.

Configuration for Entra ID

Integration type

Microsoft Entra Gallery app

Where to enable

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

SP initiated SSO. Supports automated user provisioning. Available in Microsoft Entra US Government Cloud. Configure in Lifesize Cloud Advanced Settings.

Use Stitchflow for automated provisioning.

Unlock SCIM for
Lifesize

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

Last updated: 2026-01-11

* Pricing and features sourced from public documentation.

Keep exploring

Related apps

GoTo Meeting logo

GoTo Meeting

No SCIM

Video Conferencing

ProvisioningNot Supported
Manual Cost$11,754/yr

GoTo Meeting does not support SCIM provisioning on any plan. While the platform offers SAML 2.0 SSO integration with major identity providers including Okta, Entra ID, and others, this only handles authentication—not user lifecycle management. GoTo Meeting previously supported Azure AD automatic provisioning, but this feature has been deprecated, leaving IT teams with only manual provisioning or GoTo's AD Connector v2 for limited automation. For organizations seeking true SCIM provisioning, GoTo recommends upgrading to GoToConnect (their unified communications platform that includes GoToMeeting functionality), but this forces teams into a completely different product suite. This creates a significant gap for organizations that need GoTo Meeting specifically for video conferencing but require automated user provisioning. IT teams must either manually manage user accounts—creating compliance risks and operational overhead—or invest in GoToConnect's broader platform just to access SCIM capabilities. The deprecated Azure provisioning particularly impacts Microsoft-centric organizations that were relying on this integration for user lifecycle management.

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