Scribe User Management API Guide

Auth method: Not documented

User object field mapping is not yet verified for this app.

Endpoint coverage is not yet verified for this app.

• Rate limits: Not documented

• Rate-limit headers: No

• Retry-After header: No

• Rate-limit notes: Not documented

• Pagination method: none

• Default page size: 0

• Max page size: 0

• Pagination pointer: Not documented

• Webhooks available: No

• Webhook notes: No webhook or event-streaming API is documented in Scribe's official help center or developer resources as of the policy date.

• Alternative event strategy: SCIM provisioning via IdP (Okta, Entra ID, OneLogin) is the only documented programmatic user lifecycle mechanism.

• SCIM available: Yes

• SCIM version: 2.0

• Plan required: Enterprise Grid module

• Endpoint: Not documented

• Supported operations: Create user, Deactivate user, Update user attributes

Limitations:

• SCIM endpoint URL is not publicly documented; provisioned via IdP connector setup coordinated through success@scribehow.com.
• SSO (SAML) must be configured before SCIM can be enabled.
• Supported IdPs are Okta, Microsoft Entra ID (Azure AD), and OneLogin; Google Workspace is not listed as supported.
• No public SCIM bearer token self-service generation documented; token is provided during Enterprise onboarding.
• Group provisioning support scope is not explicitly documented in public help articles.

Three IdPs are documented as supported: Okta, Microsoft Entra ID, and OneLogin.

Google Workspace is not listed.

For Okta: confirm Enterprise Grid and active SAML SSO, then contact success@scribehow.com for the tenant SCIM base URL and bearer token.

Enter both in the Okta app integration, enable Push Users (and optionally Push Groups), then assign users or groups to trigger provisioning.

Provisioning silently fails if SSO is not active at the time of the first sync.

For Entra ID deprovisioning: remove the user from the Scribe app assignment;

Entra ID sends a SCIM PATCH (active: false) or DELETE to the Scribe endpoint.

Whether Scribe treats this as a soft-deactivate or a hard-delete is not publicly documented - confirm with Scribe support before any bulk deprovisioning run.

For OneLogin attribute sync: map standard SCIM attributes (email, display name) in the OneLogin connector.

Unsupported attributes are silently ignored;

the full supported attribute schema is not publicly available.

Provision users via Okta SCIM

1. Ensure Enterprise Grid plan is active and SAML SSO is configured for the Scribe Okta app.
2. Contact success@scribehow.com to request the tenant SCIM base URL and bearer token.
3. In Okta Admin Console, navigate to the Scribe app integration and enable SCIM provisioning.
4. Enter the SCIM base URL and bearer token provided by Scribe support.
5. Enable 'Push Users' and optionally 'Push Groups' in the Okta provisioning settings.
6. Assign users or groups to the Scribe app in Okta to trigger provisioning.

Watch out for: The SCIM endpoint and token are not self-service; they must be obtained from Scribe support. Provisioning will silently fail if SSO is not active.

Deprovision a user via Entra ID (Azure AD)

1. Confirm SCIM is configured in the Scribe Enterprise app registration in Entra ID.
2. Remove the user from the Scribe application assignment in Entra ID.
3. Entra ID sends a SCIM PATCH (active: false) or DELETE to the Scribe SCIM endpoint.
4. Verify the user's access is revoked in the Scribe admin console.

Watch out for: Scribe's documented behavior on hard-delete vs. soft-deactivate via SCIM is not explicitly stated in public docs; confirm with Scribe support before bulk deprovisioning.

Sync user profile attributes via OneLogin

1. Configure the Scribe SCIM connector in OneLogin using the endpoint URL and token from Scribe support.
2. Map OneLogin user attributes (e.g., email, display name) to SCIM standard attributes.
3. Trigger a manual sync or wait for the scheduled provisioning cycle.
4. Confirm attribute updates are reflected in Scribe user profiles.

Watch out for: Only attributes supported by Scribe's SCIM schema will be accepted; unsupported attributes are silently ignored. The exact supported attribute list is not publicly documented.

The primary integration trap is assuming SCIM setup is self-service. The tenant-specific SCIM endpoint URL and bearer token are not generated in the admin console - they are provisioned by Scribe support during Enterprise onboarding, creating a hard dependency on a support ticket before any automation can be tested.

Teams that skip confirming SSO is fully active before enabling SCIM will encounter silent provisioning failures with no error surfaced in the IdP.

A second trap is scope ambiguity: group provisioning support is not explicitly documented, so IdP group-push behavior should be validated in a staging assignment before production rollout.

There are also no documented rate limits, retry headers, or API versioning semantics for the SCIM interface, which means any integration built on top of it has no published SLA to design against.