Summary and recommendation
Document360, the knowledge base platform used by technical writing teams and support organizations, does not support SCIM provisioning on any plan. While Document360 offers SAML 2.0 and OpenID Connect SSO with auto-registration for readers on Enterprise plans, this only handles authentication for existing users—not automated user lifecycle management. IT teams still face the manual burden of creating, updating, and deprovisioning user accounts across both internal team members and external documentation readers.
This creates a significant operational gap for organizations managing documentation access at scale. Reader access management becomes particularly challenging when dealing with customer-facing documentation that requires frequent access changes. Without SCIM, IT teams must manually coordinate user provisioning with documentation administrators, leading to delayed access for new team members and potential security risks from orphaned accounts when employees leave. The auto-registration feature helps with initial access but doesn't address ongoing lifecycle management or bulk user operations.
The strategic alternative
Document360 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? | Yes |
| SSO available? | Yes |
| SSO protocol | SAML 2.0, OpenID Connect |
| Documentation | Not available |
Supported identity providers
| IdP | SSO | SCIM | Notes |
|---|---|---|---|
| Okta | Via third-party | ❌ | SSO via SAML 2.0 or OpenID Connect with Okta documented. No SCIM provisioning available. Auto-registration for SSO readers supported. |
| Microsoft Entra ID | Via third-party | ❌ | SSO tutorial available in Microsoft docs. No SCIM provisioning. JIT provisioning via auto-registration only. |
| 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 Document360 accounts manually. Here's what that costs:
The Document360 pricing problem
Document360 gates SCIM provisioning behind premium plans, forcing significant cost increases for basic user management.
Tier comparison
| Plan | Price | SSO | SCIM |
|---|---|---|---|
| Standard plans | Custom quote | ||
| Enterprise | Custom quote |
Pricing structure
| Plan | Price | SSO | SCIM |
|---|---|---|---|
| Standard plans | Custom quote | ||
| Enterprise | Custom quote |
Document360 pricing context
What this means in practice
Without SCIM, IT teams managing Document360 face several operational challenges:
Reader access management issues
Manual deprovisioning risks
Additional constraints
Summary of challenges
- Document360 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 Document360 actually offers for identity
SAML 2.0 & OpenID Connect SSO (Enterprise tier)
Document360 supports federated authentication through both SAML and OpenID Connect:
| Setting | Details |
|---|---|
| Protocol | SAML 2.0 or OpenID Connect (mutually exclusive) |
| Supported IdPs | Okta, Entra ID, Auth0, ADFS, Google, generic SAML/OIDC |
| JIT Provisioning | ✓ Auto-registration for SSO readers |
| SP-initiated | ✓ Yes |
| Multiple endpoints | ✓ Yes |
Key limitation: You can use either SAML or OpenID Connect, but not both simultaneously. JWT authentication can coexist with either protocol.
What's Missing: User Lifecycle Management
Document360's identity features stop at authentication. There's no SCIM provisioning documented anywhere:
| SCIM Feature | Document360 |
|---|---|
| Create users | ❌ No |
| Update user attributes | ❌ No |
| Deactivate users | ❌ No |
| Group management | ❌ No |
| Role assignment | ❌ No |
The problem: While auto-registration handles initial user creation via SSO, you have no automated way to manage user attributes, roles, or deactivation. When someone leaves your organization or changes roles, you're back to manual administration in Document360's interface.
For documentation platforms where reader access often spans multiple teams and external stakeholders, this creates significant administrative overhead as your user base grows.
What IT admins are saying
Document360's lack of automated user provisioning forces IT teams into manual processes:
- Every user must be manually added to Document360 before they can use SSO
- No way to automatically sync team changes from your identity provider
- Reader access management becomes a bottleneck for support and documentation teams
- Offboarding requires manual cleanup in Document360 separate from IdP deprovisioning
Auto-registration is available for SSO readers... User accounts must exist in Document360 to use single sign-on for team members.
SAML and OpenID are mutually exclusive and cannot be used together.
The recurring theme
Document360 offers SSO authentication but stops short of true provisioning automation. IT teams still manage user lifecycle manually, creating operational overhead every time someone joins the documentation team or needs reader access.
The decision
| Your Situation | Recommendation |
|---|---|
| Small documentation team (<10 writers) | Manual management with SSO is workable |
| Internal docs with stable team | Use SAML/OIDC SSO with auto-registration |
| External knowledge base with reader churn | Use Stitchflow: reader access automation essential |
| Enterprise with compliance requirements | Use Stitchflow: audit trail and deprovisioning critical |
| Multi-brand documentation sites | Use Stitchflow: centralized identity management required |
The bottom line
Document360 offers solid SSO with auto-registration, but lacks SCIM provisioning entirely. For organizations managing external readers or needing automated deprovisioning for compliance, Stitchflow delivers the identity automation that Document360 simply doesn't provide.
Make Document360 workflows AI-native
Document360 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
- SCIM provisioning not documented
- SAML and OpenID are mutually exclusive (cannot use both)
- JWT can coexist with SAML/OpenID
Documentation not available.
Configuration for Entra ID
Integration type
Microsoft Entra Gallery app
Prerequisite
SSO must be configured before enabling SCIM.
Where to enable
SSO tutorial available in Microsoft docs. No SCIM provisioning. JIT provisioning via auto-registration only.
Use Stitchflow for automated provisioning.
Unlock SCIM for
Document360
Document360 has no native SCIM. We still automate end-to-end workflows across every app, including the ones without APIs.
See how it works
