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 required | Unknown |
| SSO required first? | Yes |
| SSO available? | Yes |
| SSO protocol | SAML 2.0, SWA |
| Documentation | Official docs |
Supported identity providers
| IdP | SSO | SCIM | Notes |
|---|---|---|---|
| Okta | ✓ | ✓ | OIN app with full provisioning |
| Microsoft Entra ID | ✓ | ❌ | SSO only |
| Google Workspace | ✓ | JIT only | SAML SSO with just-in-time provisioning |
| OneLogin | ✓ | ✓ | Supported |
The cost of not automating
Without SCIM (or an alternative like Stitchflow), your IT team manages Namely accounts manually. Here's what that costs:
The Namely pricing problem
Namely gates SCIM provisioning behind premium plans, forcing significant cost increases for basic user management.
Tier comparison
| Plan | Price | SSO | SCIM |
|---|---|---|---|
| Namely Now | $9/employee/mo | ||
| Namely Plus | Custom pricing | ||
| Namely Plus People | Custom pricing | ||
| Namely Complete | Custom pricing |
Plan Structure
| Plan | Price | SCIM |
|---|---|---|
| Namely Now | $9/employee/mo | ✓ |
| Namely Plus | Custom pricing | ✓ |
| Namely Plus People | Custom pricing | ✓ |
| Namely Complete | Custom 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
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:
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.
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.
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 Situation | Recommendation |
|---|---|
| Using Namely as your HRIS, need to provision employees INTO other apps | Use Okta HR-driven IT: Namely → Okta → downstream apps |
| Need to provision users INTO Namely from your IdP | Use Stitchflow: cleaner than reverse-direction SCIM setup |
| Already have Namely + Okta integration working | Keep native setup: it's built for this workflow |
| Using Entra ID and need Namely provisioning | Use Stitchflow: Entra lacks native Namely SCIM support |
| Small HR team, infrequent hires | Manual 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.
Technical specifications
SCIM Version
2.0
Supported Operations
Create, Update, Deactivate, Groups
Supported Attributes
Not specifiedPlan 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
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
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


