Summary and recommendation
DISCO, the eDiscovery platform used by law firms and corporate legal departments, does not offer SCIM provisioning on any plan. While DISCO supports SAML-based SSO with identity providers like Okta and Azure AD, this only handles authentication for existing users. User accounts must still be created and managed manually through DISCO's interface, with SSO configured per email domain rather than through centralized provisioning protocols.
This creates a significant operational burden for legal IT teams managing large case teams or frequent personnel changes. Without automated provisioning, administrators must manually create accounts for new attorneys, paralegals, and contractors, then remember to deprovision access when cases close or team members leave. Given DISCO's role in handling sensitive litigation data, manual user management introduces both security risks and compliance gaps that legal teams cannot afford.
The strategic alternative
DISCO 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 |
| Documentation | Not available |
Supported identity providers
| IdP | SSO | SCIM | Notes |
|---|---|---|---|
| Okta | ✓ | ❌ | SSO via SAML supported. No OIN connector for provisioning. |
| Microsoft Entra ID | ✓ | ❌ | SSO via SAML with Azure AD as IdP. No SCIM provisioning. |
| 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 DISCO accounts manually. Here's what that costs:
The DISCO pricing problem
DISCO gates SCIM provisioning behind premium plans, forcing significant cost increases for basic user management.
Tier comparison
| Plan | Price | SSO | SCIM |
|---|---|---|---|
| Pro | Not disclosed | ||
| Business | Not disclosed | ||
| Enterprise | Custom per-GB pricing |
Pricing and provisioning availability
| Plan | Price | SSO | SCIM |
|---|---|---|---|
| Pro | Not disclosed | ||
| Business | Not disclosed | ||
| Enterprise | Custom per-GB pricing |
Pricing transparency issues
What this means in practice
Without SCIM provisioning, IT administrators must handle all user management tasks manually:
For legal teams handling sensitive eDiscovery data, this manual overhead creates both operational burden and compliance risk.
Additional constraints
Summary of challenges
- DISCO 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 DISCO actually offers for identity
SAML SSO (All plans)
DISCO supports basic SAML 2.0 integration with identity providers:
| Setting | Details |
|---|---|
| Protocol | SAML 2.0 |
| Supported IdPs | Okta, Azure AD, ADFS |
| Configuration | Domain-based SSO setup |
| User requirement | Manual account creation required |
| Provisioning | None - SSO authentication only |
Critical limitation: DISCO's SSO is authentication-only. Users must be manually created in DISCO before they can authenticate via SSO. There's no automated user lifecycle management.
Okta Integration Status
| Feature | Supported? |
|---|---|
| SAML SSO | ✓ Yes |
| OIN connector | ❌ No |
| Create users | ❌ No |
| Update users | ❌ No |
| Deactivate users | ❌ No |
| Group mapping | ❌ No |
Azure AD Integration Status
| Feature | Supported? |
|---|---|
| SAML SSO | ✓ Yes |
| Gallery app | ❌ No |
| User provisioning | ❌ No |
| Group sync | ❌ No |
| Attribute mapping | ❌ No |
The reality: DISCO provides basic federated authentication but zero provisioning capabilities. IT teams still handle all user lifecycle tasks manually - creating accounts, updating roles, and deactivating users when they leave. For an eDiscovery platform handling sensitive legal data, this manual overhead creates both operational burden and security gaps.
What IT admins are saying
DISCO's lack of automated provisioning forces IT teams into manual account management workflows:
- Manual user creation required even with SSO configured
- No visibility into who has access without logging into DISCO directly
- Deprovisioning requires remembering to manually remove users from yet another system
- Custom per-GB pricing model makes budgeting difficult without sales engagement
SSO via SAML only - supports Okta, Azure AD, ADFS but no automated provisioning means we're still managing users manually in DISCO.
Enterprise managed services at $250/hr just to help with basic configuration feels excessive when other eDiscovery platforms include this.
The recurring theme
DISCO treats SSO and user provisioning as separate problems. IT teams get single sign-on but must still manually create, update, and remove user accounts in DISCO whenever their team changes.
The decision
| Your Situation | Recommendation |
|---|---|
| Small legal team (<10 users) with stable roster | Manual management is workable |
| Mid-size firm with quarterly litigation waves | Use Stitchflow: user scaling automation essential |
| Enterprise legal department (50+ users) | Use Stitchflow: automation required for compliance |
| Multi-matter teams with external counsel access | Use Stitchflow: complex access patterns need automation |
| Firms with strict audit requirements | Use Stitchflow: automated provisioning creates audit trail |
The bottom line
DISCO offers powerful eDiscovery capabilities but provides no identity automation—just SAML SSO with manual user management. For legal teams managing complex access patterns across multiple matters and external counsel, Stitchflow delivers the SCIM-level provisioning automation that DISCO should have built.
Make DISCO workflows AI-native
DISCO 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 native SCIM endpoint
- SSO via SAML only - supports Okta, Azure AD, ADFS
- No Okta OIN or Entra gallery connector
- Custom per-GB pricing requires sales contact
- SSO configured per email domain
- Enterprise managed services available at $250/hr
Documentation not available.
Unlock SCIM for
DISCO
DISCO has no native SCIM. We still automate end-to-end workflows across every app, including the ones without APIs.
See how it works


