diff --git a/docs/api/workflows/kubeconfigs.md b/docs/api/workflows/kubeconfigs.md
index e5e92a391a9..ee76b4d8d8a 100644
--- a/docs/api/workflows/kubeconfigs.md
+++ b/docs/api/workflows/kubeconfigs.md
@@ -29,8 +29,7 @@ kubectl patch feature ext-kubeconfigs -p '{"spec":{"value":false}}'
 
 ## Creating a Kubeconfig
 
-Admins can delete any Kubeconfig, while regular users can only delete their own. When a Kubeconfig is deleted, the kubeconfig tokens are also deleted.
-E.g. using a service account `system:admin` will lead to the following error: 
+Only a **valid and active** Rancher user can create a Kubeconfig. For example, trying to create a Kubeconfig using a `system:admin` service account will lead to an error:
 
 ```bash
 kubectl create -o jsonpath='{.status.value}' -f -<<EOF
diff --git a/versioned_docs/version-2.12/api/workflows/kubeconfigs.md b/versioned_docs/version-2.12/api/workflows/kubeconfigs.md
index e5e92a391a9..ee76b4d8d8a 100644
--- a/versioned_docs/version-2.12/api/workflows/kubeconfigs.md
+++ b/versioned_docs/version-2.12/api/workflows/kubeconfigs.md
@@ -29,8 +29,7 @@ kubectl patch feature ext-kubeconfigs -p '{"spec":{"value":false}}'
 
 ## Creating a Kubeconfig
 
-Admins can delete any Kubeconfig, while regular users can only delete their own. When a Kubeconfig is deleted, the kubeconfig tokens are also deleted.
-E.g. using a service account `system:admin` will lead to the following error: 
+Only a **valid and active** Rancher user can create a Kubeconfig. For example, trying to create a Kubeconfig using a `system:admin` service account will lead to an error:
 
 ```bash
 kubectl create -o jsonpath='{.status.value}' -f -<<EOF