Slite User Management API Guide

Auth method: API Key (Bearer token)

Setup steps

1. Log in to Slite as a workspace admin.
2. Navigate to Settings > API & Integrations.
3. Generate an API key; store it securely.
4. Pass the key as a Bearer token in the Authorization header: 'Authorization: Bearer '.

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

Endpoint coverage is not yet verified for this app.

• Rate limits: No publicly documented rate limits found in official Slite developer docs.

• Rate-limit headers: No

• Retry-After header: No

• Rate-limit notes: Rate limit details are not published in official documentation as of research date.

• Pagination method: none

• Default page size: 0

• Max page size: 0

• Pagination pointer: Not documented

• Webhooks available: No

• Webhook notes: No webhook support for user-management events is documented in official Slite developer or help center documentation.

• Alternative event strategy: Use SCIM provisioning via a supported IdP (Okta, Entra ID) to receive push-based user lifecycle events.

• SCIM available: Yes

• SCIM version: 2.0

• Plan required: Enterprise

• Endpoint: Not documented

• Supported operations: Create user, Update user, Deactivate/deprovision user, List users

Limitations:

• Requires SSO to be configured as a prerequisite before enabling SCIM.
• SCIM endpoint URL is generated per-workspace inside the Slite admin settings; it is not a static public URL.
• Only Okta and Entra ID (Azure AD) are confirmed as supported IdPs; Google Workspace and OneLogin are not listed.
• Group provisioning support is not explicitly confirmed in official documentation.
• Enterprise plan required; exact pricing is custom/unlisted.

Three integration patterns are relevant depending on tier and IdP.

On Enterprise with Okta: configure SAML/OpenID SSO first, generate SCIM credentials in Slite admin, add the Slite SCIM app in Okta, and enable Create Users, Update User Attributes, and Deactivate Users

group assignment in Okta then pushes users to Slite.

On Enterprise with Entra ID: the same credential-generation flow applies;

deprovisioning is triggered by removing the user from the Slite app assignment in Entra ID, which sends a SCIM PATCH (active: false) or DELETE.

Below Enterprise, no API path exists for user invitations;

the admin UI is the only option.

In all SCIM scenarios, deprovisioned users retain their created content - Slite does not automatically reassign owned documents on deactivation.

Provision users via Okta SCIM

1. Upgrade workspace to Enterprise plan and configure SSO (SAML/OpenID) with Okta.
2. In Slite admin settings, navigate to SCIM Provisioning and generate a SCIM bearer token and endpoint URL.
3. In Okta, add the Slite SCIM application and enter the endpoint URL and bearer token.
4. Enable provisioning features: Create Users, Update User Attributes, Deactivate Users.
5. Assign users or groups in Okta to push them to Slite.

Watch out for: SSO must be active before SCIM setup; disabling SSO after enabling SCIM may break provisioning.

Deprovision a user via Entra ID (Azure AD) SCIM

1. Ensure Slite Enterprise plan with Entra ID SSO configured.
2. In Slite admin, generate SCIM credentials and configure the Entra ID enterprise application with those credentials.
3. Remove the user from the Slite application assignment in Entra ID.
4. Entra ID sends a SCIM PATCH (active: false) or DELETE to Slite, deactivating the user.

Watch out for: Deprovisioned users may retain content they created; Slite does not automatically reassign owned documents on deactivation.

Manually invite a user without SCIM (non-Enterprise)

1. Log in as workspace admin.
2. Navigate to Settings > Members.
3. Use the 'Invite members' UI to send email invitations.
4. No API endpoint is available for this operation on non-Enterprise plans.

Watch out for: There is no public REST API for user invitations; manual UI is the only option below Enterprise tier.

The core architectural caveat for any identity graph integration is that Slite's user management surface is entirely SCIM-dependent, with no fallback REST API for user lifecycle operations. Any identity graph pipeline that assumes REST-based user provisioning will find no supported endpoint to call.

SSO misconfiguration or disabling SSO post-SCIM-setup will silently break provisioning without a documented recovery path. Group provisioning support is not confirmed in official documentation, so group-to-role mapping logic cannot be assumed.

Rate limits are undocumented, pagination is absent from the public API, and no retry-after headers are published - all of which require defensive implementation patterns when building any automated sync against Slite's SCIM layer.