For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Book a demoLog inStart for free
  • Getting started
    • Overview
    • How it works
    • Quickstart
    • Project structure
    • Customer showcase
    • Changelog
  • Configuration
    • Overview
    • Site-level settings
    • Page-level settings
  • Writing content
    • Markdown basics
    • Rich media in Markdown
    • Fern Editor
    • Reusable snippets
  • AI features
    • Overview
    • Fern Writer
    • AI-generated examples
    • Markdown access
      • Overview
      • Customize LLM output
      • Agent directives
      • Analytics and integration
    • MCP server
    • API catalog discovery
      • Overview
        • Password protection
        • SSO
        • JWT
        • OAuth
  • Public API
    • GETJWT from Fern API key
    • GETAlgolia search credentials
    • GETCurrent user information
  • Fern Writer API
    • GETGet Fern Writer Install Link
Checking status...
SOC2Soc 2 Type II
© 2026 Fern • Birch Solutions, Inc., a Postman company

Documentation

SDKsDocsAsk FernCLI Reference

API Definitions

OpenAPIAsyncAPIOpenRPCgRPC

Resources

BlogSupportPricing

Company

Brand KitPrivacy PolicyTerms of Service
LogoLogo
Book a demoLog inStart for free
On this page
  • How it works
  • Setup
AuthenticationSetup

Single Sign-On

Secure access to your documentation using corporate credentials
||View as Markdown|
Was this page helpful?
Edit this page
Previous

Password protection

Next

Set up JWT

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.

Architecture diagram

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.