Update docs

josevalim · josevalim · commit 784c039f8270 · 2026-05-19T14:20:46.000+02:00
diff --git a/README.md b/README.md
@@ -244,7 +244,7 @@ The following environment variables can be used to configure Livebook on boot:
 
   * `LIVEBOOK_IDENTITY_PROVIDER` - controls whether Zero Trust Authentication
     must be used for this Livebook instance. This is useful when deploying
-    Livebook airgapped inside a cloud platform, such as Cloudflare and Google.
+    Livebook inside a cloud platform, such as Cloudflare and Google.
     Supported values are:
 
       * `basic_auth:<username>:<password>`
diff --git a/docs/authentication.md b/docs/authentication.md
@@ -2,23 +2,23 @@
 
 Livebook has three levels of authentication:
 
-  * **Instance authentication**: this authenticates the user on all routes of your Livebook instance, including deployed notebooks and the admin section. We provide a variety of authentication options here, including Single Sign On (SSO) and domain-based authentication via [Livebook Teams](https://livebook.dev/teams), as well as Zero Trust Authentication for airgapped environments. See the "Instance authentication" section for more information.
+  * **Instance authentication**: this authenticates the user on all routes of your Livebook instance, including deployed notebooks and the admin section. See the "Instance authentication" section for more information.
 
   * **Admin authentication**: this authenticates access to Livebook admin interface within an instance, where users can create, write, and manage notebooks. Both password and token authentication are available. See the ["Admin authentication"](#admin-authentication) section for more information.
 
   * **Deployed notebook passwords**: additionally, when deploying notebooks as applications, each application may be password protected with a unique password. Only users authenticated as admin or with the password will be able to access them.
 
 ## Instance authentication
 
-When using [Livebook Teams](https://livebook.dev/teams), you can easily deploy instances of Livebook to run as application servers or as development servers. Those instances will, by default, use Livebook Teams to authenticate. The following authentication methods are supported by Livebook Teams:
+You can configure Livebook with different instance authentication mechanisms by setting the `LIVEBOOK_IDENTITY_PROVIDER` provider environment variable. The supported values are:
 
-* **Livebook Teams account**: allow members of your Livebook Teams organization to authenticate using their Livebook Teams accounts.
+  * `basic_auth:<username>:<password>`
+  * `cloudflare:<your-team-name (domain)>`
+  * `google_iap:<your-audience (aud)>`
+  * `tailscale:<tailscale-cli-socket-path>`
+  * `custom:YourElixirModule`
 
-* **Email domain**: allow users to authenticate using email accounts from specific domains, such as your company’s Google Workspace domain.
-
-* **[OpenID Connect Single Sign-On (SSO)](/oidc_sso.html)**: Allow users to authenticate via an OpenID Connect Single Sign-On provider, such as Okta, Microsoft Entra or Keycloak.
-
-If your application servers must run in an airgapped environments and cannot reach out to Livebook Teams servers, we also provide a variety of options that can be configured directly in your Dockerfiles. See the "Airgapped Authentication" section in the sidebar.
+See the "Zero Trust Authentication" section in the sidebar.
 
 ## Admin authentication
 
diff --git a/docs/authentication/basic_auth.md b/docs/authentication/basic_auth.md
@@ -5,11 +5,3 @@ Setting up Basic Authentication is a simple mechanism for protecting all routes
 ## How to
 
 To integrate Basic Authentication with Livebook, set the `LIVEBOOK_IDENTITY_PROVIDER` environment variable to `basic_auth:<username>:<password>`, and then deploy or directly run your Livebook instance.
-
-## Livebook Teams
-
-[Livebook Teams](https://livebook.dev/teams/) users can deploy notebooks with the click of a button with built-in authentication via Livebook Teams. You can also pre-configure environment variables (such as `LIVEBOOK_IDENTITY_PROVIDER`), share team secrets, and file storages. Both online and airgapped deployment mechanisms are supported.
-
-Furthermore, if you are deploying multi-session apps via [Livebook Teams](https://livebook.dev/teams/), you can programmatically access data from the authenticated user by calling [`Kino.Workspace.app_info/0`](https://hexdocs.pm/kino/Kino.Workspace.html#app_info/0).
-
-To get started, open up Livebook, click "Add Organization" on the sidebar. Then, inside the notebook of your choice, click "Deploy with Livebook Teams".
diff --git a/docs/authentication/cloudflare.md b/docs/authentication/cloudflare.md
@@ -14,11 +14,3 @@ https://developers.cloudflare.com/cloudflare-one/glossary/#team-name.
 
 For more information about Cloudflare Zero Trust, see:
 https://developers.cloudflare.com/cloudflare-one/.
-
-## Livebook Teams
-
-[Livebook Teams](https://livebook.dev/teams/) users can deploy notebooks with the click of a button with built-in authentication via Livebook Teams. You can also pre-configure environment variables (such as `LIVEBOOK_IDENTITY_PROVIDER`), share team secrets, and file storages. Both online and airgapped deployment mechanisms are supported.
-
-Furthermore, if you are deploying multi-session apps via [Livebook Teams](https://livebook.dev/teams/), you can programmatically access data from the authenticated user by calling [`Kino.Workspace.app_info/0`](https://hexdocs.pm/kino/Kino.Workspace.html#app_info/0).
-
-To get started, open up Livebook, click "Add Organization" on the sidebar. Then, inside the notebook of your choice, click "Deploy with Livebook Teams".
diff --git a/docs/authentication/google_iap.md b/docs/authentication/google_iap.md
@@ -14,11 +14,3 @@ For more information about Google IAP, see https://cloud.google.com/iap/docs/con
 Only access with Google accounts is supported. See https://cloud.google.com/iap/docs/authenticate-users-google-accounts.
 
 For more details about how to find your JWT audience, see https://cloud.google.com/iap/docs/signed-headers-howto and look for "Signed Header JWT Audience."
-
-## Livebook Teams
-
-[Livebook Teams](https://livebook.dev/teams/) users can deploy notebooks with the click of a button with built-in authentication via Livebook Teams. You can also pre-configure environment variables (such as `LIVEBOOK_IDENTITY_PROVIDER`), share team secrets, and file storages. Both online and airgapped deployment mechanisms are supported.
-
-Furthermore, if you are deploying multi-session apps via [Livebook Teams](https://livebook.dev/teams/), you can programmatically access data from the authenticated user by calling [`Kino.Workspace.app_info/0`](https://hexdocs.pm/kino/Kino.Workspace.html#app_info/0).
-
-To get started, open up Livebook, click "Add Organization" on the sidebar. Then, inside the notebook of your choice, click "Deploy with Livebook Teams".
diff --git a/docs/authentication/tailscale.md b/docs/authentication/tailscale.md
@@ -57,11 +57,3 @@ else
     [ -z "$tailscale_ip" ] && echo "- Could not determine Tailscale IP"
 fi
 ```
-
-## Livebook Teams
-
-[Livebook Teams](https://livebook.dev/teams/) users can deploy notebooks with the click of a button with built-in authentication via Livebook Teams. You can also pre-configure environment variables (such as `LIVEBOOK_IDENTITY_PROVIDER`), share team secrets, and file storages. Both online and airgapped deployment mechanisms are supported.
-
-Furthermore, if you are deploying multi-session apps via [Livebook Teams](https://livebook.dev/teams/), you can programmatically access data from the authenticated user by calling [`Kino.Workspace.app_info/0`](https://hexdocs.pm/kino/Kino.Workspace.html#app_info/0).
-
-To get started, open up Livebook, click "Add Organization" on the sidebar. Then, inside the notebook of your choice, click "Deploy with Livebook Teams".
diff --git a/docs/deployment/docker.md b/docs/deployment/docker.md
@@ -139,12 +139,10 @@ data:
 
 The setup above does not set up a data directory, which means once you restart the instance, any configuration will be lost. If you have a persistent volume, you can point the `LIVEBOOK_DATA_PATH` environment variable to it.
 
+You may also want to configure [both instance and admin authentication](authentication.md).
+
 ## Deploy notebooks as applications
 
 It is possible to deploy any notebook as an application in Livebook. To do so, choose a notebook, open up the Application pane on the sidebar (with a rocket icon), click "Manual Docker deployment", and follow the required steps for your desired platform.
 
-If you are using [Livebook Teams](https://livebook.dev/teams/), you can also deploy with the click of a button by running Livebook servers inside your infrastructure. To get started, open up Livebook and click "Add Organization" on the sidebar. Once completed, open up the Application pane on the sidebar (with a rocket icon), click "Deploy with Livebook Teams", and follow the deployment steps.
-
-The deployment steps will show you to deploy your notebooks within Docker, Fly.io, and Kubernetes. This is effectively done by setting the `LIVEBOOK_TEAMS_AUTH`, which configures Livebook to run as a read-only instance connected to Livebook Teams.
-
-Livebook Teams also support airgapped deployments, pre-configured environment variables, shared team secrets, file storages, and more.
+When deploying notebooks as applications, you may also want to configure [both instance and admin authentication](authentication.md).
diff --git a/mix.exs b/mix.exs
@@ -274,7 +274,7 @@ defmodule Livebook.MixProject do
       groups_for_extras: [
         "Livebook Teams": Path.wildcard("docs/teams/*"),
         Deployment: Path.wildcard("docs/deployment/*"),
-        "Airgapped Authentication": Path.wildcard("docs/authentication/*")
+        "Zero Trust Authentication": Path.wildcard("docs/authentication/*")
       ]
     ]
   end

Original file line number	Diff line number	Diff line change
`@@ -274,7 +274,7 @@ defmodule Livebook.MixProject do`
`274`	`274`	`groups_for_extras: [`
`275`	`275`	`"Livebook Teams": Path.wildcard("docs/teams/*"),`
`276`	`276`	`Deployment: Path.wildcard("docs/deployment/*"),`
`277`		`- "Airgapped Authentication": Path.wildcard("docs/authentication/*")`
	`277`	`+ "Zero Trust Authentication": Path.wildcard("docs/authentication/*")`
`278`	`278`	`]`
`279`	`279`	`]`
`280`	`280`	`end`