Stitchflow
Tines logo

Tines SCIM guide

Native SCIM

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

Native SCIM requires Enterprise plan

Summary and recommendation

Tines supports native SCIM 2.0 provisioning, but only on Enterprise plans with custom pricing. The platform requires SSO configuration as a prerequisite before enabling SCIM, and Community (free) tier users are locked out entirely from automated provisioning capabilities.

This creates a significant barrier for security teams evaluating Tines for workflow automation. Moving from Community to Enterprise purely for SCIM access forces organizations into enterprise sales cycles and custom pricing negotiations, often adding tens of thousands in annual costs. Meanwhile, manual user management in a security orchestration platform creates operational overhead and potential access control gaps—exactly what you're trying to eliminate with automation tools.

The strategic alternative

Tines gates SCIM behind Enterprise. Skip the Enterprise plan upgrade and automate complete outcomes across your stack. We maintain the integration layer underneath. You focus on judgment, not plumbing.

Quick SCIM facts

SCIM available?Yes
SCIM tier requiredEnterprise
SSO required first?Yes
SSO available?Yes
SSO protocolSAML 2.0
DocumentationNot available

Supported identity providers

IdPSSOSCIMNotes
OktaOIN app with full provisioning
Microsoft Entra IDSSO only
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 Tines 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 Tines pricing problem

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

Plan Structure

PlanPriceSSOSCIM
CommunityFree
ProN/A
BusinessN/A
EnterpriseCustom

Note: Pro and Business pricing details are not publicly available, but SCIM access is exclusively available in the Enterprise tier.

What this means in practice

No transparent pricing path: Unlike most SaaS tools with published tier pricing, Tines requires sales engagement and custom quotes for Enterprise access. This creates uncertainty around:

Minimum commitment requirements
Enterprise deals typically involve substantial minimum spends
Contract terms
Custom pricing often comes with multi-year commitments
Feature bundling
You pay for the full Enterprise package even if you only need SCIM

Community tier limitations: Organizations using the free Community tier face a significant jump to Enterprise for basic provisioning capabilities.

Additional constraints

SSO prerequisite
SCIM configuration requires SSO to be set up first, adding implementation complexity.
Limited IdP support
While Okta provides full SCIM support, Microsoft Entra ID only supports SSO via SAML - no provisioning integration available.
Custom pricing opacity
Without published Enterprise pricing, budgeting and procurement become unpredictable processes.
All-or-nothing access
No middle-tier option for organizations that need SCIM but not full Enterprise governance features.

Summary of challenges

  • Tines supports SCIM but only at Enterprise tier (Custom)
  • 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

Tines doesn't sell SCIM à la carte. It's bundled with Enterprise features that require custom pricing:

SCIM 2.0 automated provisioning
SAML single sign-on (SSO) - required prerequisite
Advanced team management and role-based access controls
Enterprise-grade security features and compliance tools
Dedicated customer success and support
Custom integrations and professional services
Advanced workflow automation capabilities
Enhanced monitoring and audit logging

Stitchflow Insight

The Enterprise tier targets security teams at large organizations that need comprehensive SOAR (Security Orchestration, Automation and Response) capabilities. If you're a smaller team that just wants automated user provisioning for your security workflows, you're paying for enterprise security features, custom support tiers, and advanced automation tools you likely don't need. We estimate ~80% of Enterprise features are irrelevant for teams that only need SCIM provisioning.

What IT admins are saying

Community sentiment on Tines's SCIM limitations reveals mixed experiences. Common complaints:

  • Enterprise tier requirement creating cost barriers for smaller security teams
  • Lack of SCIM support in Microsoft Entra ID despite SSO availability
  • Having to implement SSO first before accessing SCIM functionality
  • Custom Enterprise pricing making budget planning difficult

We're stuck on the Community tier because Enterprise pricing is out of reach, but we really need automated user provisioning for our security workflows.

Reddit r/SecurityArchitecture

Tines works great with Okta SCIM but there's no provisioning support for Azure AD. We're a Microsoft shop so that's frustrating.

Spiceworks Community

The recurring theme

SCIM availability varies dramatically by IdP, and Enterprise tier requirements create artificial barriers for teams that need automated provisioning but don't require other Enterprise features.

The decision

Your SituationRecommendation
On Community/Pro/Business, need SCIMUse Stitchflow: avoid the Enterprise tier jump and custom pricing
Already on Enterprise with SCIMUse native SCIM: you're paying for it
Using Entra ID and need provisioningUse Stitchflow: Tines only supports Entra SSO, not provisioning
Need Enterprise security features beyond SCIMEvaluate Enterprise: SCIM comes bundled with the tier
Small security team, low employee churnManual may work: but monitor for access gaps as you scale

The bottom line

Tines gates SCIM behind Enterprise custom pricing, and only supports provisioning from Okta—leaving Entra ID customers without native options. For teams that need automated provisioning without Enterprise costs or across multiple IdPs, Stitchflow delivers SCIM-level automation at a predictable price.

Make Tines workflows AI-native

Tines gates SCIM behind Enterprise. We build complete offboarding, user access reviews, and license workflows without that SCIM Tax upgrade.

No Enterprise upgrade required
Less than a week, start to finish (~2 hours of your time)
We maintain the integration layer underneath
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

  • Enterprise tier required for SCIM
  • SSO configuration required before SCIM
  • Community (free) tier has limited features

Documentation not available.

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 → Tines → 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 provisioning support

Tines gates SCIM behind Enterprise. Stitchflow automates complete workflows without that SCIM Tax upgrade.

Unlock SCIM for
Tines

Tines gates SCIM behind Enterprise plan. We automate complete offboarding and access reviews across your stack without that SCIM Tax upgrade.

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

Last updated: 2026-01-20

* Pricing and features sourced from public documentation.

Keep exploring

Related apps

Alteryx logo

Alteryx

SCIM Tax
SCIM StatusIncluded
Manual Cost$9,490/yr

Alteryx supports native SCIM 2.0 provisioning, but only on Enterprise plans with custom pricing (7+ users minimum). The feature requires SSO (SAML or OIDC) to be configured first and completely overrides manual user management. For teams on Professional ($5,000/user/year) or Business ($10,000-$20,000/user/year) plans, accessing SCIM means upgrading to Enterprise - often a significant cost increase for functionality that should be table stakes. This creates a provisioning gap for most Alteryx deployments. Without automated user lifecycle management, IT teams face manual onboarding/offboarding workflows, delayed access provisioning, and compliance risks around orphaned accounts. The high per-user costs make Alteryx particularly expensive to scale, and forcing an Enterprise upgrade just for basic provisioning automation compounds that challenge.

View full guide
Atlan logo

Atlan

SCIM Tax
SCIM StatusIncluded
Manual Cost$9,490/yr

Atlan supports native SCIM 2.0 provisioning with full user and group management capabilities. However, SCIM is only available on Enterprise tier, which requires custom pricing negotiations. Additionally, SSO must be enabled before SCIM can be configured, and Atlan's pricing tiers (Starter, Premier, Enterprise) are not publicly disclosed, making cost planning difficult for IT teams. This creates a significant barrier for organizations wanting automated provisioning without committing to enterprise-level contracts. For data teams evaluating Atlan, the lack of transparent pricing means you can't budget for provisioning capabilities upfront. The SSO prerequisite also forces organizations into a specific implementation sequence that may not align with their rollout timeline.

View full guide
Benchling logo

Benchling

SCIM Tax
SCIM StatusIncluded
Manual Cost$9,490/yr

Benchling supports SCIM provisioning, but only on Enterprise plans with custom pricing that typically starts at $1M+ annually. This creates a massive barrier: organizations on Professional plans ($20,000+/year) face a 50x+ price increase to unlock automated user provisioning. Even mid-sized life sciences teams end up paying enterprise-level licensing just to automate basic user lifecycle management. The pricing gap is so extreme that most organizations either stick with manual provisioning or delay Benchling adoption entirely. This creates a significant operational burden for IT teams managing researchers across multiple lab environments. Manual user provisioning in a platform that handles sensitive R&D data introduces compliance risks and delays researcher onboarding. When a scientist joins or leaves, IT must manually coordinate access across Benchling's complex permission structure for notebooks, entities, and workflows. For organizations with frequent collaborator access or seasonal research teams, this becomes unmanageable.

View full guide