Integration

SCIM provisioning
for GitBook

GitBook has no native SCIM. SCIM.ninja adds it — so your identity provider can keep GitBook access in sync automatically.

Get started free Book a demo
How it works

There's a better way

GitBook doesn't offer SCIM — but it does have an API. SCIM.ninja wraps it in a compliant SCIM 2.0 endpoint, so your IdP can provision it like any SCIM-native app.

Built on GitBook's existing API
There's no native SCIM to wait on. We connect through GitBook's API and expose a standard SCIM 2.0 endpoint on top of it.
Standard SCIM 2.0 — no IdP changes needed
Point Okta, Entra ID, or Google Workspace at your SCIM.ninja endpoint. Your IdP config stays exactly the same.
Add, update, and deactivate automatically
When someone joins, is updated, or leaves in your directory, their GitBook access follows in real time.
Managed setup
We build and validate the GitBook connection for you as part of onboarding — at no extra cost.
Custom attributes

Sync more than the basics

Native integrations usually push just a name and an email. SCIM.ninja maps every attribute your directory holds — job title, department, manager, and custom fields — so GitBook always has the full picture of who each user is.

Why it matters

No SCIM means manual work — and risk

Without SCIM, every GitBook member is invited, updated, and removed by hand. New hires wait for access to your docs, records drift out of date, and people who've left can keep reading internal documentation long after their last day. Automating it from your directory closes those gaps.

FAQ

Frequently asked questions

Does GitBook support SCIM provisioning?
Not natively — GitBook has no built-in SCIM endpoint. SCIM.ninja adds standards-based SCIM 2.0 provisioning on top of GitBook's API, so your identity provider can manage GitBook access automatically.
Do I need to change anything in GitBook?
No major changes. We connect through GitBook's API using credentials you control, then expose a standard SCIM endpoint to your IdP. We handle the configuration and testing during onboarding.
Which identity providers are supported?
Any IdP that speaks SCIM 2.0 — including Okta, Microsoft Entra ID (Azure AD), Google Workspace, JumpCloud, and OneLogin.
What gets synced to GitBook?
User accounts and their attributes: people are provisioned when they join, kept in sync while they're active, and deactivated when they're deprovisioned in your directory.
How long does setup take?
Typically 24–48 hours from when you share your GitBook details. Once it's live, you get a 7-day free trial to verify everything in your environment before billing starts.
Explore

More from SCIM.ninja

Use Case 01

Add SCIM compatibility to any app

Learn more Use Case 02

Beat the SCIM tax

Learn more

Ready to automate GitBook provisioning?

Connect your identity provider to GitBook — no native SCIM required.

Get started free Book a demo