Summary and recommendation
Smokeball, the legal practice management platform, does not support SCIM provisioning on any plan tier. While Smokeball offers SAML 2.0 SSO integration through Microsoft Entra (Azure AD), this only handles authentication for existing users—not automated user lifecycle management. All user provisioning, deprovisioning, and profile updates must be handled manually within Smokeball's admin interface, creating significant operational overhead for law firms managing multiple attorneys, paralegals, and support staff.
This limitation creates a compliance risk for legal practices, where timely user deprovisioning is critical when staff leave the firm. Manual processes increase the likelihood of orphaned accounts with access to sensitive client data and case files. For growing legal practices or multi-office firms, the administrative burden of managing user accounts across Smokeball and other legal technology tools becomes unsustainable.
The strategic alternative
Smokeball 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 required | N/A |
| SSO required first? | No |
| SSO available? | Yes |
| SSO protocol | SAML 2.0 (via Microsoft Entra) |
| Documentation | Not available |
Supported identity providers
| IdP | SSO | SCIM | Notes |
|---|---|---|---|
| Okta | Via third-party | ❌ | No Smokeball integration in Okta OIN. |
| Microsoft Entra ID | ✓ | ❌ | SSO supported via Microsoft Entra. No SCIM provisioning available. |
| 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 Smokeball accounts manually. Here's what that costs:
The Smokeball pricing problem
Smokeball gates SCIM provisioning behind premium plans, forcing significant cost increases for basic user management.
Tier comparison
| Plan | Price | SSO | SCIM |
|---|---|---|---|
| Bill | $49/user/mo | ||
| Boost | Custom quote | ||
| Grow | Custom quote | ||
| Prosper+ | Custom quote |
Pricing and provisioning availability
| Plan | Price | SSO | SCIM |
|---|---|---|---|
| Bill | $49/user/mo | ||
| Boost | Custom quote | ||
| Grow | Custom quote | ||
| Prosper+ | Custom quote |
What this means in practice
Manual user lifecycle management: IT teams must manually create, update, and deactivate Smokeball accounts for lawyers, paralegals, and legal staff. There's no way to sync user attributes, group memberships, or automate onboarding/offboarding processes.
Microsoft Entra dependency: SSO is exclusively available through Microsoft Entra (Azure AD). Firms using other identity providers like Okta, Google Workspace, or OneLogin cannot implement single sign-on without additional identity bridging solutions.
No visibility into access: Without SCIM, you can't programmatically audit who has access to what legal cases or client data within Smokeball, creating compliance risks for law firms handling sensitive client information.
Additional constraints
Summary of challenges
- Smokeball 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 Smokeball actually offers for identity
SAML SSO (via Microsoft Entra only)
Smokeball provides limited single sign-on capabilities exclusively through Microsoft Entra (Azure AD):
| Setting | Details |
|---|---|
| Protocol | SAML 2.0 |
| Supported IdPs | Microsoft Entra (Azure AD) only |
| Configuration | Must use Microsoft Entra integration |
| User requirement | Manual user creation required in Smokeball |
Critical limitation: Smokeball's SSO is restricted to Microsoft Entra environments. Organizations using Okta, Google Workspace, or OneLogin cannot implement federated authentication.
No provisioning capabilities
Smokeball offers zero automated user management:
| Feature | Supported? |
|---|---|
| SCIM provisioning | ❌ No |
| Create users | ❌ No |
| Update users | ❌ No |
| Deactivate users | ❌ No |
| Group sync | ❌ No |
| JIT provisioning | ❌ No |
The reality: Every user account must be manually created, updated, and deactivated in Smokeball. When lawyers join or leave your firm, IT must log into Smokeball separately to manage their access—no automation exists.
Enterprise features require custom quotes
Smokeball's pricing structure limits identity management options:
For legal practices that need streamlined user management across multiple systems, Smokeball's manual-only approach creates ongoing administrative overhead that scales poorly as firms grow.
What IT admins are saying
Smokeball's lack of SCIM provisioning creates ongoing manual work for IT teams managing legal practices:
- Manual user provisioning required - every new hire must be added to Smokeball separately
- No automated deprovisioning when employees leave the firm
- Limited to Microsoft Entra for SSO, excluding other identity providers
- Enterprise features require custom quotes, making budgeting difficult
SSO setup uses Microsoft Entra (Azure AD)
The recurring theme
Even with SSO configured through Microsoft Entra, IT teams must manually create, update, and remove user accounts in Smokeball. This creates security risks when departing employees aren't promptly deprovisioned and administrative overhead for every staff change.
The decision
| Your Situation | Recommendation |
|---|---|
| Small law firm (<10 users) with stable staff | Manual user management is acceptable |
| Mid-sized firm using Microsoft Entra for other apps | Manual management with SSO for authentication |
| Large legal practice (25+ users) with regular staff changes | Use Stitchflow: automation essential for managing legal staff turnover |
| Multi-office law firm with complex org structure | Use Stitchflow: automation strongly recommended |
| Enterprise legal department with compliance requirements | Use Stitchflow: automation essential for audit trail and governance |
The bottom line
Smokeball is built for legal practice management but stuck in the past when it comes to identity management. With no SCIM support and only basic SSO through Microsoft Entra, every user addition, role change, or departure requires manual intervention. For legal practices that need automated provisioning without the administrative overhead, Stitchflow delivers the modern identity management that Smokeball doesn't.
Make Smokeball workflows AI-native
Smokeball has no native SCIM. We build complete offboarding, user access reviews, and license workflows across every app, including the ones without APIs.
Technical specifications
SCIM Version
Not specifiedSupported Operations
Not specifiedSupported Attributes
Plan requirement
Not specifiedPrerequisites
Not specifiedKey limitations
- No SCIM provisioning
- SSO via Microsoft Entra (Azure AD)
- Contact vendor for enterprise features
Documentation not available.
Configuration for Entra ID
Integration type
Microsoft Entra Gallery app
Where to enable
SSO supported via Microsoft Entra. No SCIM provisioning available.
Use Stitchflow for automated provisioning.
Unlock SCIM for
Smokeball
Smokeball has no native SCIM. We still automate end-to-end workflows across every app, including the ones without APIs.
See how it works


