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. That leaves a workflow gap in offboarding, access reviews, and license cleanup unless your team handles the app another way. Stitchflow builds and maintains the IT workflows your team still runs manually, across every app, including the ones without APIs.
Quick SCIM facts
| SCIM available? | No |
| SCIM tier required | N/A |
| SSO required first? | No |
| SSO available? | Yes |
| SSO protocol | OIDC |
| Documentation | Not available |
Supported identity providers
| IdP | SSO | SCIM | Notes |
|---|---|---|---|
| Okta | Via third-party | ❌ | SSO via OIDC (OpenID Connect). Schema discovery supported. User provisioning listed as 'coming soon'. Requires subdomain (company.proposify.com). |
| Microsoft Entra ID | Via third-party | ❌ | Azure AD SSO via OIDC (not SAML). Requires custom App Registration. User provisioning not available. Requires subdomain setup. |
| Google Workspace | Via third-party | ❌ | No native support |
| OneLogin | Via third-party | ❌ | No 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:
The Proposify pricing problem
Proposify gates SCIM provisioning behind premium plans, forcing significant cost increases for basic user management.
Tier comparison
| Plan | Price | SSO | SCIM |
|---|---|---|---|
| Basic | $29/month (2 users) | ||
| Team | $49/month (unlimited users) | ||
| Business | $65/month + $780/year per additional user |
Pricing and provisioning options
| Plan | Price | SSO | SCIM |
|---|---|---|---|
| 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:
For a 50-person sales team, this creates 200+ manual tasks per year just for basic provisioning.
Additional constraints
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:
| Setting | Details |
|---|---|
| Protocol | OpenID Connect (OIDC) |
| Supported IdPs | Okta, Salesforce, Azure AD |
| Configuration | Requires custom subdomain (company.proposify.com) |
| User requirement | Manual 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:
| Feature | Supported? |
|---|---|
| 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
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'
Azure AD SSO via OIDC (not SAML). Requires custom App Registration.
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 Situation | Recommendation |
|---|---|
| Small sales team (<10 users) with stable headcount | Manual management is acceptable |
| Growing sales organization (20+ users) | Use Stitchflow: manual provisioning doesn't scale |
| High sales rep turnover or seasonal hiring | Use Stitchflow: automation essential for rapid onboarding |
| Enterprise with compliance requirements | Use Stitchflow: automation essential for audit trail |
| Multi-team deployment (sales, BizDev, account management) | Use Stitchflow: automation strongly recommended |
The bottom line
Proposify has no native SCIM. That means one more workflow gap in offboarding, access reviews, and license cleanup unless your team handles it another way.
Close the Proposify workflow gap
Proposify is one gap in a broader workflow. Stitchflow builds and maintains the offboarding, access review, or license workflow across every app in your environment.
Technical specifications
SCIM Version
Not specifiedSupported Operations
Not specifiedSupported Attributes
Plan requirement
Not specifiedPrerequisites
Not specifiedKey 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
Docs
SSO via OIDC (OpenID Connect). Schema discovery supported. User provisioning listed as 'coming soon'. Requires subdomain (company.proposify.com).
Use Stitchflow for automated provisioning.
Close the workflow gap in
Proposify
Proposify has no native SCIM. That leaves one more workflow gap in offboarding, access reviews, and license cleanup unless your team handles it another way.
Start with the free gap diagnostic


