Stitchflow
Harness logo

Harness SCIM guide

Native SCIM

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

Native SCIM requires Enterprise plan

Summary and recommendation

Harness supports SCIM 2.0 for automated user and group provisioning, but only on Enterprise plans with custom pricing. While SCIM handles creating, updating, and deactivating users from your IdP, it doesn't provision role bindings or permissions—those must be configured separately within Harness after users are synced. This creates a significant gap in true automated provisioning for DevOps teams.

The result is a two-step provisioning process: SCIM syncs the user accounts, but administrators still need to manually assign roles, project access, and pipeline permissions within Harness. For organizations with multiple clusters or complex role hierarchies, this manual overhead defeats much of the automation benefit. SSO with JIT provisioning is available but provides even less control over user lifecycle management.

The strategic alternative

Stitchflow provides SCIM-level provisioning through resilient browser automation for Harness that handles both user sync and role assignment workflows. Works with any Harness plan and any IdP. Flat pricing under $5K/year with 24/7 human-in-the-loop support to manage the complex permission mappings that native SCIM leaves behind.

Quick SCIM facts

SCIM available?Yes
SCIM tier requiredEnterprise
SSO required first?Yes
SSO available?Yes
SSO protocolSAML 2.0
DocumentationOfficial docs

Supported identity providers

IdPSSOSCIMNotes
OktaOIN app with full provisioning
Microsoft Entra IDGallery app with SCIM
Google WorkspaceJIT onlySAML SSO with just-in-time provisioning
OneLoginSupported

The cost of not automating

Without SCIM (or an alternative like Stitchflow), your IT team manages Harness 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 Harness pricing problem

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

Plan Structure

PlanPriceSSOSCIM
Free$0 (2,000 cloud credits/mo)
TeamContact for pricing (up to 100 services)
EnterpriseCustom pricing (annual subscription)

What this means in practice

Harness follows the "contact sales" model for Enterprise pricing, making cost evaluation difficult. Based on industry standards for DevOps platforms:

Pricing opacity
No public Enterprise pricing means lengthy sales cycles just to understand costs
All-or-nothing jump
Teams using the free tier or Team plan must upgrade to the most expensive tier for SCIM
Annual commitment
Enterprise requires annual subscription, eliminating monthly flexibility

The modular pricing approach means you pay only for needed modules, but SCIM access still requires Enterprise-level commitment across all modules you use.

Additional constraints

Role binding gap
SCIM only handles user and group provisioning - role assignments and permissions must be configured separately in Harness after provisioning
Cluster-specific setup
Each Harness cluster requires its own SCIM URL configuration, adding complexity for multi-cluster deployments
API key management
SCIM integration requires maintaining API keys with user/group permissions, creating additional security overhead
Limited IdP flexibility
While SAML SSO works with any IdP, full SCIM 2.0 is documented only for Okta and Azure AD

Summary of challenges

  • Harness supports SCIM but only at Enterprise tier (Custom pricing (annual subscription, all modules available))
  • Google Workspace users get JIT provisioning only, not full SCIM
  • Our research shows teams manually provisioning this app spend significant hidden costs annually

What the upgrade actually includes

Harness doesn't sell SCIM separately. It's bundled with Enterprise features across their modular platform:

SCIM 2.0 automated provisioning (users and groups)
SAML single sign-on (SSO)
Advanced role-based access control (RBAC)
Policy as Code governance
Audit trails and compliance reporting
Service reliability management
Custom dashboards and analytics
Dedicated support with SLAs

The catch: SCIM only handles user/group sync. Role bindings and permissions must be configured separately in Harness after provisioning. You're also locked into cluster-specific SCIM URLs and API key management.

Stitchflow Insight

If you need enterprise DevOps governance anyway, the upgrade delivers value. If you just want automated user provisioning, you're paying for enterprise features most teams don't need. We estimate ~60% of Enterprise capabilities are overkill for organizations that only want basic identity automation.

What IT admins are saying

Community sentiment on Harness's SCIM implementation is mixed, with admins appreciating the functionality but frustrated by the operational complexity. Common complaints:

  • SCIM doesn't handle role bindings, requiring manual permission management after provisioning
  • Cluster-specific SCIM URLs create configuration overhead for multi-environment setups
  • Enterprise tier requirement locks out smaller DevOps teams from automated provisioning
  • Split workflow between identity sync and role assignment increases administrative burden

SCIM provisioning works well for getting users into Harness, but then you're back to manual work assigning roles and permissions. It's only half the automation story.

DevOps Lead, Reddit

Having to configure separate SCIM endpoints for each cluster is a pain when you're managing multiple environments. Wish it was more centralized.

Platform Engineer, GitHub Issues

The recurring theme

While Harness offers solid SCIM functionality, the separation between user provisioning and role management creates a two-step process that undermines the efficiency gains teams expect from automation.

The decision

Your SituationRecommendation
Not on Enterprise tierUse Stitchflow: avoid the Enterprise upgrade just for SCIM
On Enterprise but need role automationUse Stitchflow: automate role bindings that native SCIM can't handle
Already on Enterprise with simple role needsUse native SCIM: you're paying for it already
Managing multiple Harness clustersUse Stitchflow: avoid configuring cluster-specific SCIM URLs
Small DevOps team with stable membershipManual may work: but watch for permission gaps as you scale

The bottom line

Harness locks SCIM behind Enterprise tier pricing and doesn't automate role bindings—leaving you with half-solved provisioning. Stitchflow provides complete automation including role assignments at flat pricing that works with any Harness plan.

Automate Harness without the tier upgrade

Stitchflow delivers SCIM-level provisioning through resilient browser automation, backed by 24/7 human in the loop for Harness at <$5K/year, flat, regardless of team size.

Works alongside or instead of native SCIM
Syncs with your existing IdP (Okta, Entra ID, Google Workspace)
Automates onboarding and offboarding
SOC 2 Type II certified
24/7 human-in-the-loop monitoring
Book a Demo

Technical specifications

SCIM Version

2.0

Supported Operations

Create, Update, Deactivate, Groups

Supported Attributes

Not specified

Plan requirement

Enterprise

Prerequisites

SSO must be configured first

Key limitations

  • SCIM does not handle role bindings
  • Permissions managed separately in Harness
  • API key with user/group permissions required
  • Cluster-specific SCIM URL required

Configuration for Okta

Integration type

Okta Integration Network (OIN) app with SCIM provisioning

Prerequisite

SSO must be configured before enabling SCIM.

Where to enable

Okta Admin Console → Applications → Harness → Provisioning

Required credentials

SCIM endpoint URL and bearer token (generated in app admin console).

Configuration steps

Enable Create Users, Update User Attributes, and Deactivate Users.

Provisioning trigger

Okta provisions based on app assignments (users or groups).

Full SCIM 2.0 provisioning for users and groups. Cluster-specific SCIM URL required. SCIM does not handle role bindings - permissions managed separately in Harness.

Native SCIM is available on Enterprise. Use Stitchflow if you need provisioning without the tier upgrade.

Configuration for Entra ID

Integration type

Microsoft Entra Gallery app with SCIM provisioning

Prerequisite

SSO must be configured before enabling SCIM.

Where to enable

Entra admin center → Enterprise applications → Harness → Provisioning

Required credentials

Tenant URL (SCIM endpoint) and Secret token (bearer token from app admin console).

Configuration steps

Set Provisioning Mode = Automatic, configure SCIM connection.

Provisioning trigger

Entra provisions based on user/group assignments to the enterprise app.

Sync behavior

Entra provisioning runs on a scheduled cycle (typically every 40 minutes).

Full SCIM 2.0 provisioning. Requires API key with user/group permissions. Role bindings managed separately in Harness after provisioning.

Native SCIM is available on Enterprise. Use Stitchflow if you need provisioning without the tier upgrade.

Unlock SCIM for
Harness

Harness gates automation behind Enterprise plan. Stitchflow delivers the same SCIM outcomes for a flat fee.

See how it works
Admin Console
Directory
Applications
Harness logo
Harness
via Stitchflow

Last updated: 2026-01-11

* Pricing and features sourced from public documentation.

Keep exploring

Related apps

Amplitude logo

Amplitude

SCIM Tax

Product Analytics

SCIM StatusIncluded
Manual Cost$11,754/yr

Amplitude supports SCIM provisioning, but only on Growth plans (starting around $36K/year) or Enterprise plans with custom pricing. While Amplitude's SCIM implementation covers the core functionality—creating, updating, and deactivating users—it requires SCIM to be specifically enabled for your organization, and regenerating the SCIM key immediately invalidates existing integrations without warning. For product teams on Plus plans ($49/month), upgrading to Growth just to unlock SCIM means jumping from under $600/year to $36,000+/year—a 60x increase. That's often more than the entire analytics budget for smaller product teams. The gap becomes particularly problematic for cross-functional product teams where analysts, PMs, and engineers need varying levels of access to user behavior data, but manual provisioning creates security risks around sensitive analytics permissions.

View full guide
Bugsnag logo

Bugsnag

SCIM Tax

Error Monitoring / Observability

SCIM StatusIncluded
Manual Cost$11,754/yr

Bugsnag supports native SCIM provisioning, but only on Enterprise plans with custom pricing. This creates a significant cost barrier since you must upgrade from Business ($475/month for 1M events) to Enterprise just to unlock automated user provisioning. For many engineering teams, this represents a substantial price jump for provisioning features that should be standard across all paid plans. The Enterprise requirement is particularly problematic for mid-size development teams who need error monitoring automation but don't require Enterprise-level features. Without SCIM, IT teams must manually provision developer accounts and manage team memberships for project access—creating security gaps when developers change teams or leave the company. OneLogin users face an additional limitation: SCIM isn't supported on Enterprise instances, forcing a workaround through the standard Bugsnag app.

View full guide
Greenhouse logo

Greenhouse

SCIM Tax

HR / Recruiting

SCIM StatusIncluded
Manual Cost$11,754/yr

Greenhouse supports SCIM provisioning, but only on Advanced or Expert tiers (starting around $6,000/year, quote-based). The bigger issue: Greenhouse's SCIM implementation only provisions users—not groups—meaning you lose the organizational structure and permission inheritance that makes identity management scalable. Additionally, you cannot fully delete users via SCIM (only deactivate), and Azure Entra users face a 40-minute sync delay. For recruiting teams managing hiring managers, interviewers, and HR staff across different departments and access levels, the lack of group provisioning creates a significant operational burden. You're forced to manually assign permissions and manage access changes for every user individually. With recruiting involving sensitive candidate data and frequent access changes during hiring cycles, this manual overhead increases both security risk and administrative workload.

View full guide