AuthenticationSetup

Single Sign-On

Secure access to your documentation using corporate credentials
View as Markdown
Enterprise feature

This feature is available only for the Enterprise plan. To get started, reach out to support@buildwithfern.com.

SSO lets your team access your docs through your organization’s identity provider using SAML 2.0 or OIDC. Like RBAC and API key injection, SSO uses the fern_token cookie to identify authenticated users. SSO unlocks the Fern Editor for browser-based editing and authenticated preview links.

SSO provides login-based access control but does not support role management or API key injection. For granular access control, use RBAC instead.

How it works

When a user clicks Login, Fern redirects them to your identity provider. After authenticating with their corporate credentials, the identity provider redirects back to Fern with a fern_token, granting access to your docs.

Setup

Fern supports any SAML 2.0 or OIDC provider (Okta, Google Workspace, Auth0, Azure AD, OneLogin, etc.). Contact Fern or reach out via Slack. Fern will work with your security team to connect to your identity provider.