You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: fern/products/docs/pages/authentication/overview.mdx
+12-11Lines changed: 12 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,28 +3,29 @@ title: Overview of authentication options
3
3
description: Understand the different authentication options Fern offers
4
4
---
5
5
6
-
Fern offers two methods of authentication, Single Sign-On (SSO) and Role-Based Access Control (RBAC).
6
+
Fern supports three ways to restrict access to your documentation:
7
7
8
-
**For most situations, use RBAC** for granular access control over your documentation. RBAC works well for sites with multiple audiences (internal teams, partners, customers) and supports API key injection to autopopulate code examples.
9
-
10
-
API key injection can be set up using either JWT or OAuth, depending on your existing authentication system.
11
-
12
-
**SSO is simpler** but only provides basic login functionality - it doesn't support RBAC or API key injection. SSO works well for internal-only documentation where everyone should see the same content.
8
+
-**RBAC** — Control which content different users can see. Supports [API key injection](/learn/docs/authentication/api-key-injection) via JWT or OAuth. Recommended for most use cases.
9
+
-**SSO** — Require login without role management. Good for internal docs where all users see the same content.
10
+
-**Password protection** — A single shared password for the entire site. Good for pre-release docs or basic access restriction.
13
11
14
12
<Note>
15
13
Learn how Fern handles user credentials and authentication in the [Security overview](/learn/docs/security/overview).
subtitle: Protect your documentation site with a shared password for simple access control.
4
+
---
5
+
6
+
<Markdownsrc="/snippets/enterprise-plan.mdx"/>
7
+
8
+
Password protection allows you to restrict access to your documentation site using a shared password. This is useful for pre-release documentation, internal resources, or any content you want to keep private without requiring individual user accounts.
9
+
10
+
## How it works
11
+
12
+
When password protection is enabled, visitors to your documentation site are prompted to enter a password before they can view any content. Once authenticated, users can browse the site until their session expires.
13
+
14
+
## Setting up password protection
15
+
16
+
To enable password protection for your documentation site, [contact Fern](https://buildwithfern.com/contact) or reach out via Slack. Fern will configure the password for your site.
0 commit comments