diff --git a/docs/platform/enterprise-cloud-ui/configure.mdx b/docs/platform/enterprise-cloud-ui/configure.mdx
index 95a52664..9a3f5620 100644
--- a/docs/platform/enterprise-cloud-ui/configure.mdx
+++ b/docs/platform/enterprise-cloud-ui/configure.mdx
@@ -271,8 +271,8 @@ browser always loads them over the same protocol it uses to access the Cloud UI
 The Cloud UI resolves the Registry Server API URL dynamically:
 
 1. If an [Enterprise Manager](../enterprise-manager/index.mdx) is configured and
-   the [registry policy](../enterprise-manager/policies/registry.mdx) has an
-   `api_url` value, the Cloud UI uses that URL.
+   the [registry policy](../enterprise-manager/policies/registry.mdx) has a
+   `server_api_url` value, the Cloud UI uses that URL.
 2. Otherwise, the Cloud UI falls back to the `API_BASE_URL` environment
    variable.
 
diff --git a/docs/platform/enterprise-manager/policies/registry.mdx b/docs/platform/enterprise-manager/policies/registry.mdx
index b19d887a..82cde165 100644
--- a/docs/platform/enterprise-manager/policies/registry.mdx
+++ b/docs/platform/enterprise-manager/policies/registry.mdx
@@ -67,6 +67,32 @@ enterpriseConfig:
     enforcement: 'enforced'
 ```
 
+### Registry URL for the Cloud UI
+
+The registry directive sets two URLs because ToolHive clients and the Cloud UI
+connect to the registry differently. The `api_url` value is for ToolHive clients
+(CLI and Stacklok Desktop): depending on your registry, that's either the
+registry's root URL (as in the examples above) or a per-registry path on a
+Stacklok Registry Server (for example,
+`https://registry.example.com/registry/<REGISTRY_NAME>`). The
+[Enterprise Cloud UI](../../enterprise-cloud-ui/configure.mdx) needs the
+Registry Server's API root instead, set with `server_api_url`:
+
+```yaml title="values.yaml"
+enterpriseConfig:
+  registry:
+    value:
+      # For ToolHive clients: the registry API URL (one registry)
+      api_url: 'https://registry.example.com/registry/toolhive'
+      # For the Cloud UI: the Registry Server's API root
+      server_api_url: 'https://registry.example.com'
+    enforcement: 'enforced'
+```
+
+When `server_api_url` isn't set, the Cloud UI falls back to its `API_BASE_URL`
+environment variable (see
+[Registry API URL resolution](../../enterprise-cloud-ui/configure.mdx#registry-api-url-resolution)).
+
 ## Next steps
 
 - [Non-registry servers policy](./non-registry-servers.mdx) to control whether