Authentication for private docs

Restrict access to your docs site with password protection, SSO, or JWT tokens.

By default, Mintlify sites are publicly accessible. If your docs contain sensitive information — internal APIs, private playbooks, or unreleased product documentation — you can restrict access.

Password protection

The simplest option: set a password in Project Settings → Authentication → Password. Anyone visiting the site must enter the password before seeing any content.

Password protection is available on Growth and Enterprise plans.

SSO (SAML)

Connect your identity provider so readers must sign in with their company credentials. Available on Enterprise plans.

1. Go to Project Settings → Authentication → SSO.
2. Provide your IdP’s metadata URL or XML.
3. Map the required attributes (email, name).
4. Enable SSO enforcement.

Readers who aren’t authenticated are redirected to your IdP’s login page.

JWT tokens

For tighter integration with your own authentication system, Mintlify supports JWT-based authentication. Your backend generates a signed JWT that grants access to specific docs sections.

This approach lets you:

• Show different content to different user tiers.
• Gate specific sections of your docs behind feature flags or subscription levels.
• Integrate with your own login system without requiring a separate IdP connection.

See the Mintlify authentication documentation for JWT format requirements and example implementations.

All authentication options require the Growth or Enterprise plan. Starter sites are always publicly accessible.