Stitchflow
Namely logo

Namely SCIM guide

Native SCIM

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

Summary and recommendation

Namely supports SCIM provisioning through Okta's integration, but there's a fundamental mismatch: Namely is designed as an HR source system that provisions to other applications, not the reverse. While SCIM functionality exists, it's primarily intended for Namely to push employee data downstream to apps like Google Workspace or Office 365 via Okta's HR-driven IT provisioning workflows.

For IT teams that need to provision users into Namely from their identity provider, this creates a gap. The available SCIM support isn't designed for inbound provisioning scenarios. Plus, with pricing starting at $9/employee/month but enterprise features requiring custom pricing that typically runs $19-26 per employee per month, you're looking at significant costs for an HR platform that may not align with your provisioning architecture.

The strategic alternative

Namely gates SCIM behind Unknown. Skip the Unknown 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 requiredUnknown
SSO required first?Yes
SSO available?Yes
SSO protocolSAML 2.0, SWA
DocumentationOfficial docs

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 Namely 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 Namely pricing problem

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

Tier comparison

PlanPriceSSOSCIM
Namely Now$9/employee/mo
Namely PlusCustom pricing
Namely Plus PeopleCustom pricing
Namely CompleteCustom pricing

Plan Structure

PlanPriceSCIM
Namely Now$9/employee/mo
Namely PlusCustom pricing
Namely Plus PeopleCustom pricing
Namely CompleteCustom pricing

Note: SCIM provisioning is available across all tiers, but implementation typically requires custom pricing discussions beyond the basic Namely Now plan.

What this means in practice

The core issue isn't pricing—it's architectural:

Reverse data flow: Namely is built to be your HR master that feeds employee data to Okta for downstream provisioning. If you need to provision users INTO Namely from your IdP, you're working against the intended workflow.

Limited Entra ID support: While Okta has full SCIM integration, Microsoft Entra ID only supports SSO. This creates a gap for organizations using Entra as their primary IdP.

HR-centric onboarding: New employees are typically added to Namely by HR first, then synced outward—not provisioned inward from IT systems.

Additional constraints

Implementation costs
Custom pricing typically includes 10-25% implementation fees on top of annual software costs.
IdP dependency
Full provisioning capabilities require Okta. Entra ID users are limited to SSO-only integration.
Workflow reversal
Using Namely as a provisioning target fights against its core design as an HR source system.
Complex pricing
Beyond the $9/mo starter tier, all plans require custom pricing negotiations.

Summary of challenges

  • Namely supports SCIM but only at Unknown tier (custom pricing)
  • Google Workspace users get JIT provisioning only, not full SCIM
  • Our research shows teams manually provisioning this app spend significant hidden costs annually

What Namely actually offers for identity

Namely is fundamentally an HR system (HRIS) that serves as an identity source, not a destination. Their SCIM integration works in reverse from most apps:

Outbound SCIM provisioning to downstream applications
HR-driven identity management
(Namely feeds other systems)
SAML SSO for employee access to Namely
Okta HR-driven IT integration for automated downstream provisioning
Employee lifecycle automation
(hire/transfer/terminate workflows)
Schema discovery for attribute mapping
Group linking for role-based access

The key limitation: Namely doesn't receive SCIM provisioning from your IdP because it's designed to be the authoritative source for employee data. Your HR team manages users in Namely, which then provisions accounts to other business applications through Okta or similar platforms.

This creates a governance challenge if you need centralized identity management across all systems, since Namely operates as an upstream source rather than participating in standard IdP-driven provisioning workflows.

What IT admins are saying

Community sentiment on Namely's role reversal is mixed, with confusion about its positioning as both an HRIS and provisioning target. Common observations:

  • Namely typically serves as the HR source system, not a downstream app
  • Most organizations use Namely to provision other applications via Okta HR-driven IT
  • Limited discussion about being provisioned TO Namely since it's usually the authoritative source
  • Pricing opacity makes it difficult to assess true SCIM costs

We're using Namely as our HRIS master to push employee data to all our other apps through Okta. It works well as the source of truth.

IT Manager, Reddit

The custom pricing on everything above the basic plan makes it impossible to budget properly. You have to go through sales just to understand what SCIM will cost.

System Administrator, Spiceworks

The recurring theme

Namely's identity in the provisioning ecosystem is backwards from most SaaS apps – it's typically the system that provisions others, not the one being provisioned to, making traditional SCIM concerns less relevant.

The decision

Your SituationRecommendation
Using Namely as your HRIS, need to provision employees INTO other appsUse Okta HR-driven IT: Namely → Okta → downstream apps
Need to provision users INTO Namely from your IdPUse Stitchflow: cleaner than reverse-direction SCIM setup
Already have Namely + Okta integration workingKeep native setup: it's built for this workflow
Using Entra ID and need Namely provisioningUse Stitchflow: Entra lacks native Namely SCIM support
Small HR team, infrequent hiresManual may work: but consider automation as you scale

The bottom line

Namely is designed as an HR source system that provisions outbound to other apps, not the reverse. For organizations that need to provision users into Namely from their IdP, Stitchflow provides the automation without fighting against Namely's intended workflow direction.

Make Namely workflows AI-native

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

No Unknown 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

Unknown

Prerequisites

SSO must be configured first

Key limitations

  • Typically an HR source system
  • Used to provision OTHER apps
  • SAML and SWA supported
  • Group linking 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 → Namely → 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 with group linking and schema discovery. Namely often used as HR source for Okta HR-driven IT provisioning.

Namely gates SCIM behind Unknown. Stitchflow automates complete workflows without that SCIM Tax upgrade.

Configuration for Entra ID

Integration type

Microsoft Entra Gallery app

Prerequisite

SSO must be configured before enabling SCIM.

Where to enable

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

Microsoft Entra ID tutorial covers SSO configuration only. SP-initiated SSO supported. No SCIM provisioning documented for Entra.

Use Stitchflow for automated provisioning.

Unlock SCIM for
Namely

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

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

Last updated: 2026-01-11

* Pricing and features sourced from public documentation.

Keep exploring

Related apps

BambooHR logo

BambooHR

No SCIM

HR / HRIS

ProvisioningNot Supported
Manual Cost$11,754/yr

BambooHR does not support inbound SCIM provisioning on any plan. While BambooHR integrates with identity providers like Okta and Entra ID, it functions as the HR source of truth that provisions users TO other systems, not the other way around. This means your IdP cannot automatically create, update, or deactivate user accounts in BambooHR based on HR events or group membership changes. BambooHR offers SAML 2.0 SSO with JIT provisioning, but this only handles authentication for users who already exist in the system. This creates a significant operational gap for IT teams managing employee lifecycle automation. While BambooHR can push employee data to your IdP when HR makes changes, there's no way to automate the reverse flow - provisioning new users into BambooHR itself still requires manual account creation or CSV imports. For organizations where BambooHR isn't the primary HR system of record, this means maintaining dual data entry processes and accepting the compliance risks that come with manual provisioning workflows.

View full guide
Personio logo

Personio

No SCIM

HR / HRIS

ProvisioningNot Supported
Manual Cost$11,754/yr

Personio, the HR information system for 10-5,000 employee companies, does not offer SCIM provisioning capabilities. Instead, Personio functions as an HR source system that syncs employee data one-way to identity providers like Okta and Microsoft Entra ID through custom API integrations. While these integrations automate employee onboarding and offboarding by pushing HR data to your IdP every 30 minutes, they don't provide the bidirectional SCIM provisioning that IT teams need to manage user access within Personio itself. Additionally, Personio only supports native SSO via OIDC (not SAML), requiring third-party bridges like JumpCloud for SAML-based SSO workflows. This creates a fundamental gap for IT teams managing Personio access. While your IdP can receive employee data from Personio, you still need manual processes to provision user accounts, assign roles, and manage permissions within Personio when employees join, change roles, or leave. For multi-entity organizations or companies requiring granular access controls, this manual overhead becomes particularly problematic, especially given Personio's Enterprise-tier pricing that averages ~$47,000 annually.

View full guide
8x8 logo

8x8

SCIM Tax

UCaaS / Business Communications

SCIM StatusIncluded
Manual Cost$11,754/yr

8x8 supports SCIM 2.0 for automated user provisioning, but only on their quote-based X Series plans (previously $24-44/user/month range before they moved to custom pricing). While SCIM can create, update, and deactivate users, it has critical gaps that create ongoing manual overhead: license assignment must be done manually after every user is provisioned, users can't be deleted (only deactivated), and provisioned users don't automatically appear in the Company Directory. For IT teams managing a unified communications platform that typically covers all employees, these limitations defeat much of SCIM's purpose. You're still manually touching every user account to assign licenses and ensure directory visibility. The lack of user deletion support also creates compliance headaches when employees leave - accounts accumulate as "deactivated" rather than being properly removed.

View full guide