Stitchflow
Lansweeper logo

Lansweeper SCIM guide

Connector Only

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

Native SCIM not available

Summary and recommendation

Lansweeper, the IT asset management and discovery platform, does not offer SCIM provisioning on any plan. While Lansweeper Cloud supports SSO via OIDC and SAML with providers like Azure AD, Google, and Okta (requiring Pro tier or higher), this only handles authentication for existing users. User accounts must still be manually created and managed within Lansweeper's interface, with no API-driven provisioning capabilities available.

This creates a significant operational burden for IT teams managing Lansweeper access across growing organizations. Without automated provisioning, IT admins must manually create accounts for new employees needing asset visibility, manually update permissions when roles change, and manually deactivate accounts during offboarding. For an asset management tool that's supposed to streamline IT operations, this manual user lifecycle management becomes increasingly problematic as teams scale beyond 50+ users.

The strategic alternative

Lansweeper 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 dedicated Lansweeper integration in Okta OIN catalog
Microsoft Entra IDSSO supported via OIDC/SAML for Lansweeper Cloud; no SCIM provisioning
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 Lansweeper 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 Lansweeper pricing problem

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

Tier comparison

PlanPriceSSOSCIM
FreeUp to 100 assets
Starter~$200/month (2K assets)
ProCustom quote (up to 9K assets)
EnterpriseCustom quote (10K+ assets)

Pricing and provisioning structure

PlanPriceSSOSCIM
FreeUp to 100 assets
Starter~$200/month (2K assets)
ProCustom quote (up to 9K assets)
EnterpriseCustom quote (10K+ assets)

What this means in practice

IT teams face several operational challenges:

Manual user management
All user creation, updates, and deactivation must be handled individually through the Lansweeper interface
No automated onboarding
New hires require manual account creation even with SSO configured
Delayed offboarding
Departing employees' access must be manually removed, creating security gaps
Inconsistent access control
Without automated provisioning, role assignments and permissions drift over time

Additional constraints

Cloud-only SSO
SSO integration only works with Lansweeper Cloud deployments, not on-premises installations
Pro tier minimum
SSO requires upgrading to Pro tier or higher, adding significant cost for smaller teams
Limited IdP documentation
While Azure AD, Google, and Okta are supported for authentication, provisioning integration guidance is sparse
Asset-focused platform
Lansweeper's core strength is IT asset discovery and inventory management, not user lifecycle management

Summary of challenges

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

SSO (Cloud only)

Lansweeper Cloud supports federated authentication through multiple protocols:

SettingDetails
ProtocolsOIDC, SAML 2.0
Supported IdPsAzure AD, Google Workspace, Okta, custom SAML/OIDC providers
ConfigurationStandard IdP metadata exchange
Deployment requirementLansweeper Cloud only (not on-premises)
Minimum tierPro tier required

Critical limitation: SSO is exclusively available for Lansweeper Cloud deployments. Organizations running on-premises Lansweeper installations cannot leverage federated authentication.

Okta Integration Status

No dedicated Lansweeper integration exists in the Okta Integration Network catalog:

FeatureSupported?
SAML SSO❌ No dedicated app
OIDC SSO❌ No dedicated app
SWA (password vaulting)❌ No dedicated app
Create users❌ No
Update users❌ No
Deactivate users❌ No
Group push❌ No

Translation: While Lansweeper Cloud can authenticate against Okta via generic OIDC/SAML, there's no streamlined Okta app template or any provisioning capabilities.

Microsoft Entra Integration

FeatureSupported?
SAML SSO✓ Yes (Cloud only)
OIDC SSO✓ Yes (Cloud only)
SCIM provisioning❌ No
User creation❌ Manual only
User updates❌ Manual only
User deactivation❌ Manual only

Reality check: Even with SSO configured, IT teams must manually provision every user account in Lansweeper. There's no automated user lifecycle management through SCIM or any other mechanism.

What IT admins are saying

Lansweeper's lack of automated user provisioning creates operational overhead for IT teams managing asset discovery workflows:

  • Manual user management required even with SSO enabled
  • No automated onboarding/offboarding for team members accessing asset data
  • Separate user administration outside of central identity management
  • Time-consuming coordination between IT asset discovery and user access control

SSO is available for Lansweeper Cloud but you still need to manually manage user accounts and permissions within the platform.

IT Administrator, Reddit

Having to remember to add/remove users in Lansweeper every time someone joins or leaves the team is just another thing on the checklist that shouldn't be there.

Systems Administrator, Spiceworks Community

The recurring theme

Even organizations using Lansweeper for comprehensive IT asset management must handle user provisioning manually, creating disconnect between their identity management strategy and asset discovery operations.

The decision

Your SituationRecommendation
Small IT team (<20 users) with stable staffManual user management is workable
Growing organization (20-100 users)Use Stitchflow: manual provisioning becomes a bottleneck
Enterprise IT operations (100+ users)Use Stitchflow: automation essential for asset discovery teams
Multi-location deployments with frequent staff changesUse Stitchflow: automation critical for operational efficiency
Compliance-driven environments requiring audit trailsUse Stitchflow: automated provisioning provides necessary documentation

The bottom line

Lansweeper is a comprehensive IT asset discovery platform, but it offers no SCIM provisioning capabilities whatsoever. Even with SSO available on higher tiers, you're stuck with manual user management. For IT operations teams that need automated provisioning to match their infrastructure automation, Stitchflow delivers SCIM-level capabilities through reliable browser automation.

Make Lansweeper workflows AI-native

Lansweeper 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 endpoint for user provisioningSSO only available for Lansweeper Cloud (not on-prem)Supports OIDC and SAML for SSOWorks with Azure AD, Google, Okta for authenticationAsset discovery and inventory management focusPro tier required for SSO and full integrations

Plan requirement

Not specified

Prerequisites

Not specified

Key limitations

  • No native SCIM endpoint for user provisioning
  • SSO only available for Lansweeper Cloud (not on-prem)
  • Supports OIDC and SAML for SSO
  • Works with Azure AD, Google, Okta for authentication
  • Asset discovery and inventory management focus
  • Pro tier required for SSO and full integrations

Documentation not available.

Unlock SCIM for
Lansweeper

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