From 64877771e16ffd81e3e831fb85a8b7533575e54f Mon Sep 17 00:00:00 2001 From: Min RK Date: Tue, 29 Oct 2024 11:38:17 +0100 Subject: [PATCH] update per review Co-authored-by: Simon Li --- docs/source/administrator/upgrading/upgrade-3-to-4.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/source/administrator/upgrading/upgrade-3-to-4.md b/docs/source/administrator/upgrading/upgrade-3-to-4.md index 865bb7c6d5..c0ce56ffa9 100644 --- a/docs/source/administrator/upgrading/upgrade-3-to-4.md +++ b/docs/source/administrator/upgrading/upgrade-3-to-4.md @@ -25,7 +25,7 @@ Especially if you use features like per-user subdomains or custom page templates ### Allowing users JupyterHub 5 promotes the `allow_all` and `allow_existing_users` configuration used on OAuthenticator to all other Authenticators. -If you have no explicitly allowed users, the default is now to allow no users (this was already the default if you were using OAuth). +If you have not explicitly allowed users, the default is to allow no users (this was already the default if you were using OAuth). If you are using an Authenticator where all users who can successfully authenticate should have access, set: ```yaml