Stitchflow
Proposify logo

Proposify SCIM guide

Connector Only

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

Summary and recommendation

Proposify, the proposal software platform, does not support SCIM provisioning on any plan. While Proposify offers SSO integration with Okta, Azure AD, and Salesforce on their Business plan ($3,900/year for 5 users), this only handles authentication through OIDC protocol—not user lifecycle management. Their Okta integration page explicitly lists user provisioning as "coming soon" with no timeline provided, leaving IT teams with manual account creation and deprovisioning processes.

This creates a significant operational gap for organizations using Proposify across sales and business development teams. Without automated provisioning, IT administrators must manually create accounts for new sales hires, update permissions when roles change, and remember to deactivate accounts when employees leave—creating both security risks and administrative overhead. The SSO integration requires custom subdomain setup (company.proposify.com) and doesn't eliminate the manual provisioning burden.

The strategic alternative

Proposify 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 protocolOIDC
DocumentationNot available

Supported identity providers

IdPSSOSCIMNotes
OktaVia third-partySSO via OIDC (OpenID Connect). Schema discovery supported. User provisioning listed as 'coming soon'. Requires subdomain (company.proposify.com).
Microsoft Entra IDVia third-partyAzure AD SSO via OIDC (not SAML). Requires custom App Registration. User provisioning not available. Requires subdomain setup.
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 Proposify 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 Proposify pricing problem

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

Tier comparison

PlanPriceSSOSCIM
Basic$29/month (2 users)
Team$49/month (unlimited users)
Business$65/month + $780/year per additional user

Pricing and provisioning options

PlanPriceSSOSCIM
Basic$29/month (2 users)
Team$49/month (unlimited users)
Business$65/month + $780/year per additional user

Key constraint: Business plan required for any SSO functionality, with a 5-user minimum at $3,900/year base cost.

What this means in practice

Without SCIM, every user lifecycle event requires manual intervention:

New hires
IT must manually create accounts in Proposify after provisioning in your IdP
Role changes
Access levels must be updated in two places independently
Terminations
Critical security gap - accounts may remain active in Proposify even after IdP deprovisioning
Bulk changes
No way to sync department moves or mass updates

For a 50-person sales team, this creates 200+ manual tasks per year just for basic provisioning.

Additional constraints

OIDC-only for Azure
Uses OpenID Connect instead of SAML, requiring custom App Registration setup
Subdomain requirement
Forces company.proposify.com subdomain structure for SSO
No JIT provisioning
Users must be manually created before they can authenticate via SSO
Okta integration gaps
User provisioning listed as "coming soon" with no delivery timeline
Pricing jump
Moving from Team ($49/month) to Business ($3,900/year) represents an 8x cost increase

Summary of challenges

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

OIDC SSO (Business plan)

Proposify supports single sign-on via OpenID Connect (OIDC) with select identity providers:

SettingDetails
ProtocolOpenID Connect (OIDC)
Supported IdPsOkta, Salesforce, Azure AD
ConfigurationRequires custom subdomain (company.proposify.com)
User requirementManual user creation required

Critical gap: Azure AD integration uses OIDC instead of the standard SAML protocol, requiring custom App Registration setup rather than standard enterprise app gallery deployment.

Okta Integration (via OIN)

The official Okta Integration Network listing for Proposify shows limited capabilities:

FeatureSupported?
SAML SSO❌ No
OIDC SSO✓ Yes
Create users❌ No (listed as "coming soon")
Update users❌ No
Deactivate users❌ No
Group push❌ No

What you actually get

SSO authentication via OIDC protocol only
Manual user provisioning and deprovisioning required
Custom subdomain setup mandatory
No automated user lifecycle management
No group-based access control

The reality: Proposify's Business plan ($3,900/year for 5 users, $780/year per additional user) gives you basic SSO but zero provisioning automation. Every user addition, role change, and offboarding remains a manual IT task.

What IT admins are saying

Community sentiment on Proposify's provisioning is mixed—SSO works, but the lack of automated user provisioning creates ongoing administrative burden:

  • Manual user creation required even with SSO configured
  • No SCIM support despite being listed as "coming soon"
  • Azure integration requires OIDC workarounds instead of standard SAML
  • Business plan requirement ($3,900/year minimum) just to get basic SSO

User provisioning listed as 'coming soon'

Okta Integration Network

Azure AD SSO via OIDC (not SAML). Requires custom App Registration.

Proposify support documentation

The recurring theme

Proposify offers functional SSO but forces IT teams into manual provisioning workflows. Even after paying for the Business plan, every user addition, role change, and departure requires manual intervention in Proposify's admin console.

The decision

Your SituationRecommendation
Small sales team (<10 users) with stable headcountManual management is acceptable
Growing sales organization (20+ users)Use Stitchflow: manual provisioning doesn't scale
High sales rep turnover or seasonal hiringUse Stitchflow: automation essential for rapid onboarding
Enterprise with compliance requirementsUse Stitchflow: automation essential for audit trail
Multi-team deployment (sales, BizDev, account management)Use Stitchflow: automation strongly recommended

The bottom line

Proposify offers solid proposal software with SSO authentication, but it lacks SCIM provisioning entirely—forcing IT teams into manual user management. For sales organizations that need streamlined user lifecycle management without the administrative overhead, Stitchflow is the clear solution.

Make Proposify workflows AI-native

Proposify 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 SCIM provisioning documentedAzure uses OIDC, not SAMLSSO requires subdomain setupBusiness plan required for SSO

Plan requirement

Not specified

Prerequisites

Not specified

Key limitations

  • No SCIM provisioning documented
  • Azure uses OIDC, not SAML
  • SSO requires subdomain setup
  • Business plan required for SSO

Documentation not available.

Configuration for Okta

Integration type

Okta Integration Network (OIN) app

Where to enable

Okta Admin Console → Applications → Proposify → Sign On

SSO via OIDC (OpenID Connect). Schema discovery supported. User provisioning listed as 'coming soon'. Requires subdomain (company.proposify.com).

Use Stitchflow for automated provisioning.

Unlock SCIM for
Proposify

Proposify 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
Proposify logo
Proposify
via Stitchflow

Last updated: 2026-01-11

* Pricing and features sourced from public documentation.

Keep exploring

Related apps

Qwilr logo

Qwilr

No SCIM

Proposal Software / Sales

ProvisioningNot Supported
Manual Cost$11,754/yr

Qwilr, the proposal creation platform used by sales and marketing teams, does not support SCIM provisioning on any plan. While Qwilr offers OAuth-based SSO integration with Okta, Entra ID, Google Workspace, and OneLogin, this only handles authentication, not user lifecycle management. Users must be manually provisioned in Qwilr first, then mapped to SSO identities. The OAuth-only approach (no SAML) also limits integration options compared to enterprise-standard SAML implementations. This creates a significant operational gap for IT teams managing growing sales organizations. OAuth SSO alone doesn't solve the core provisioning challenge—new sales hires still require manual account creation, role assignment, and access configuration in Qwilr. When team members leave or change roles, IT must remember to manually deprovision or update their Qwilr access, creating compliance risks and potential data exposure.

View full guide
6sense logo

6sense

No SCIM

B2B Revenue Intelligence / ABM

ProvisioningNot Supported
Manual Cost$11,754/yr

6sense, the B2B revenue intelligence platform, has paused SCIM provisioning for new customers until Q4 2026. While existing customers with SCIM enabled can continue using it, new implementations are limited to JIT (Just-In-Time) provisioning through SAML SSO. This creates a significant gap for IT teams managing revenue intelligence access, as JIT only creates users on first login and provides minimal attribute mapping (email, first name, last name only). For an enterprise platform with typical pricing of $55,000-$130,000 annually, the absence of automated user lifecycle management is a substantial limitation. The lack of SCIM until Q4 2026 forces IT teams into manual provisioning workflows for a platform handling sensitive revenue data. While SAML SSO handles authentication, it doesn't address user lifecycle events like role changes, department transfers, or offboarding. This creates compliance risks in revenue teams where access to prospect data and sales intelligence must be tightly controlled. The nearly two-year wait for SCIM restoration means organizations implementing 6sense today face manual user management for the foreseeable future.

View full guide
ActiveCampaign logo

ActiveCampaign

No SCIM

Marketing Automation / Email

ProvisioningNot Supported
Manual Cost$11,754/yr

ActiveCampaign, the marketing automation platform, does not offer native SCIM provisioning on any plan. While the Enterprise plan ($145+/month) includes SAML 2.0 SSO with just-in-time (JIT) provisioning, this only creates user accounts on first login—there's no automated deprovisioning when employees leave or change roles. New SSO users are automatically added to a generic "SSO Users" group with configurable permissions, but IT teams have no way to programmatically manage user lifecycles or enforce granular access controls based on department or role changes. This creates a significant gap for marketing teams that need to manage access to customer data and campaign tools. When employees leave the company or change departments, their ActiveCampaign access must be manually revoked, creating compliance risks and potential data exposure. The lack of automated deprovisioning means former employees could theoretically retain access to sensitive marketing data and customer information until someone manually removes them from the platform.

View full guide