Samepage 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 documentation found in official Samepage help center or developer resources.

• Alternative event strategy: Zapier integration may provide limited event-driven automation for content-level actions, but user lifecycle events are not documented.

• SCIM available: No
• SCIM version: Not documented
• Plan required: Pro
• Endpoint: Not documented

Limitations:

• No SCIM provisioning documented in official Samepage help center.
• SAML SSO is available on Pro/Enterprise plans (Okta and Entra ID listed as supported IdPs), but automated user provisioning via SCIM is not confirmed.
• User lifecycle management (create, deactivate, sync) must be performed manually through the Samepage admin UI.

Three lifecycle scenarios are relevant for teams evaluating Samepage programmatically.

First, onboarding: without SCIM, there is no mechanism to push new users from an IdP directory into Samepage automatically;

each user must be invited individually by email via the admin console.

Second, offboarding: revoking IdP access when SAML SSO is active will block login, but it does not remove the Samepage account

manual console removal is still required, creating a window of residual access.

Third, SSO configuration: SAML 2.0 can be configured with Okta or Entra ID via metadata exchange on Pro or Enterprise, but just-in-time provisioning support is unconfirmed in official documentation and should be verified directly with Samepage support before being relied upon.

Onboard a new employee

1. Admin logs into Samepage admin console.
2. Manually invites user by email via the Members section.
3. If SAML SSO is configured (Pro/Enterprise), user authenticates via IdP on first login.
4. No automated provisioning available; role assignment is manual.

Watch out for: Without SCIM, there is no way to automate user creation from an IdP directory; each user must be invited individually.

Offboard a departing employee

1. Admin navigates to Members in the Samepage admin console.
2. Manually removes or deactivates the user account.
3. If SAML SSO is active, revoking IdP access prevents login but does not automatically remove the Samepage account.

Watch out for: No SCIM deprovisioning means terminated employees may retain a Samepage account until manually removed, creating a security gap.

Configure SSO for centralized authentication

1. Upgrade to Pro or Enterprise plan.
2. Navigate to Admin > Security > SSO in Samepage.
3. Configure SAML 2.0 with Okta or Microsoft Entra ID using metadata exchange.
4. Test SSO login; users are authenticated via IdP but still must exist in Samepage (JIT provisioning support is unconfirmed in official docs).

Watch out for: Just-in-time (JIT) provisioning behavior is not explicitly documented; verify with Samepage support before relying on it for automated account creation.

The core integration risk is the absence of a user-management API and SCIM endpoint, which prevents Samepage from participating in an identity graph - the connected map of user states, roles, and access entitlements that automated IAM and IGA tooling depends on.

Without SCIM or webhooks exposing user lifecycle events, there is no reliable signal for when a user is created, modified, or removed in a downstream system. Zapier's Samepage integration covers content-level actions and does not expose provisioning or deprovisioning triggers.

Teams building automated access reviews or relying on directory-driven deprovisioning will need to treat Samepage as a manual exception in any orchestration pipeline until a supported API surface is published.