Skip to main content
NodePad Enterprise integrates with your existing identity provider to enforce single sign-on and automate user lifecycle management. Once configured, your team authenticates through your identity provider — not through a NodePad-managed login — and user accounts are created or deactivated automatically as your directory changes. This gives your IT and security teams a single place to control access to NodePad, consistent with how you manage every other application in your environment.

​
Single sign-on

NodePad supports SSO via two industry-standard protocols:
SAML 2.0 is supported by most enterprise identity providers. NodePad acts as the service provider (SP); your identity provider (IdP) handles authentication and issues assertions.Common SAML 2.0 identity providers that work with NodePad include:
  • Okta
  • Microsoft Entra ID (formerly Azure Active Directory)
  • Google Workspace
  • OneLogin
  • Ping Identity
  • Any other SAML 2.0-compliant IdP
When SSO is enabled, users who attempt to access NodePad without an active session are redirected to your identity provider for authentication. Passwords are managed entirely by your IdP.
You can require SSO for all users in your organization. When enforced, direct login to NodePad is disabled — users must authenticate through your identity provider.

​
SCIM directory provisioning

SCIM (System for Cross-domain Identity Management) keeps NodePad in sync with your identity directory automatically. When you add a new employee to your IdP, they get access to NodePad. When someone leaves, their account is deactivated immediately — no manual steps required.
1

Connect your identity provider

The Enterprise team configures a SCIM endpoint for your NodePad deployment. You point your IdP’s SCIM provisioning settings at this endpoint.
2

Map groups and attributes

Map your IdP groups to NodePad roles. Users inherit permissions based on the groups they belong to in your directory.
3

Enable provisioning

Once provisioning is active, new users are created in NodePad automatically when added to the relevant group in your IdP, and deprovisioned when removed.

​
Benefits

Centralized access control

NodePad access is governed by the same identity policies as the rest of your tools. Revoking access in your IdP takes effect immediately.

Automatic onboarding

New team members get NodePad access as soon as they’re added to the right group in your directory — no waiting for manual provisioning.

Instant offboarding

When an employee leaves, deactivating their IdP account deactivates their NodePad access at the same time.

Audit consistency

Authentication events flow through your identity provider’s logs, keeping NodePad access history consistent with your other applications.

​
Use your own identity provider

NodePad does not require you to use a NodePad-managed identity system. In an Enterprise deployment, your identity provider is the authoritative source for authentication. NodePad connects to it — not the other way around.
If your organization already uses Okta, Entra ID, or another SAML/OIDC provider, SSO setup is straightforward. The Enterprise team will provide configuration details specific to your IdP.

​
Get started

SSO and SCIM configuration is handled as part of your Enterprise onboarding. Contact the team to get your identity provider integration set up.

Contact the Enterprise team

Tell us which identity provider you use and the team will guide you through the SSO and SCIM setup process.