diff --git a/content/manuals/security/for-admins/hardened-desktop/settings-management/configure-json-file.md b/content/manuals/security/for-admins/hardened-desktop/settings-management/configure-json-file.md
index 9b61004cf50f..0096692d5a89 100644
--- a/content/manuals/security/for-admins/hardened-desktop/settings-management/configure-json-file.md
+++ b/content/manuals/security/for-admins/hardened-desktop/settings-management/configure-json-file.md
@@ -17,7 +17,23 @@ Settings Management is designed specifically for organizations who don’t give
 
 ## Prerequisites
 
-You first need to [enforce sign-in](/manuals/security/for-admins/enforce-sign-in/_index.md) to ensure that all Docker Desktop developers authenticate with your organization. Since Settings Management requires a Docker Business subscription, enforced sign-in guarantees that only authenticated users have access and that the feature consistently takes effect across all users, even though it may still work without enforced sign-in.
+You must [enforce sign-in](/manuals/security/for-admins/enforce-sign-in/_index.md) to ensure that all Docker Desktop users authenticate with your organization.
+
+Settings management requires a Docker Business subscription. Docker Desktop verifies the user's authentication and licensing before applying any settings from the `admin-settings.json` file. The settings file will not take effect unless both authentication and license checks pass. These checks ensure that only licensed users receive managed settings.
+
+> [!IMPORTANT]
+>
+> If a user is not signed in, or their Docker ID does not belong to an organization with a Docker Business subscription, Docker Desktop ignores the `admin-settings.json` file.
+
+
+## Known limitations
+
+The `admin-settings.json` file requires users to authenticate with Docker Hub and be a member
+of an organization with a Docker Business subscription. This means the file does not work in:
+
+- Air-grapped or offline environments where Docker Desktop can't authenticate with Docker Hub.
+- Restricted environments where SSO and cloud-based authentication are not permitted.
+
 
 ## Step one: Create the `admin-settings.json` file and save it in the correct location
 
diff --git a/hugo_stats.json b/hugo_stats.json
index a01b564ea82f..c940976a29e3 100644
--- a/hugo_stats.json
+++ b/hugo_stats.json
@@ -13,6 +13,7 @@
       "-v",
       "-z-10",
       ".NET",
+      "AWS-Route-53",
       "Admin-Console",
       "After",
       "Angular",
@@ -53,6 +54,8 @@
       "Git-Bash-CLI",
       "GitLab",
       "Go",
+      "GoDaddy",
+      "Google-Cloud-DNS",
       "HTTP",
       "Heredocs",
       "Hyper-V-backend-x86_64",
@@ -82,6 +85,7 @@
       "Okta",
       "Okta-SAML",
       "Old-Dockerfile",
+      "Other-providers",
       "PHP",
       "PowerShell",
       "PowerShell-CLI",