diff --git a/docs/clearml_agent/clearml_agent_ref.md b/docs/clearml_agent/clearml_agent_ref.md
index 17791e9c..43ee2019 100644
--- a/docs/clearml_agent/clearml_agent_ref.md
+++ b/docs/clearml_agent/clearml_agent_ref.md
@@ -110,7 +110,7 @@ clearml-agent daemon [-h] [--foreground] [--queue QUEUES [QUEUES ...]] [--order-
 |`--status`| Print the worker's schedule (uptime properties, server's runtime properties and listening queues)|<img src="/docs/latest/icons/ico-optional-no.svg" alt="No" className="icon size-md center-md" />|
 |`--stop`| Terminate a running ClearML Agent, if other arguments are the same. If no additional arguments are provided, agents are terminated in lexicographical order.|<img src="/docs/latest/icons/ico-optional-no.svg" alt="No" className="icon size-md center-md" />|  
 |`--uptime`| Specify uptime for clearml-agent in `<hours> <days>` format. For example, use `17-20 TUE` to set Tuesday's uptime to 17-20. <br/><br/>NOTES:<ul><li>This feature is available under the ClearML Enterprise plan </li><li>Make sure to configure only `--uptime` or `--downtime`, but not both.</li></ul>|<img src="/docs/latest/icons/ico-optional-no.svg" alt="No" className="icon size-md center-md" />|
-|`--use-owner-token`| Generate and use the task owner's token for the execution of the task.|<img src="/docs/latest/icons/ico-optional-no.svg" alt="No" className="icon size-md center-md" />|
+|`--use-owner-token`| Run tasks under the identity of each task's owner: all calls made by the task code during execution will use the owner's credentials instead of the agent's. See example use case under [Service Accounts](../webapp/settings/webapp_settings_users.md#service-accounts). **This feature is available under the ClearML Enterprise plan**. |<img src="/docs/latest/icons/ico-optional-no.svg" alt="No" className="icon size-md center-md" />|
 
 </div>
 
diff --git a/docs/webapp/settings/webapp_settings_users.md b/docs/webapp/settings/webapp_settings_users.md
index 4b25da31..79040699 100644
--- a/docs/webapp/settings/webapp_settings_users.md
+++ b/docs/webapp/settings/webapp_settings_users.md
@@ -95,8 +95,8 @@ vaults and to the resources that the task owner has access to. Impersonating an
 will have admin privileges (see [Setting a Service Account as Administrator](#setting-a-service-account-as-administrator)).
 
 In case impersonation is not enabled: 
-* If you run an agent with `--use_owner_token` then the agent will fail. 
-* If you run an agent without `--use_owner_token`, the task will run with the service account's access rules, so make 
+* If you run an agent with `--use-owner-token` then the agent will fail. 
+* If you run an agent without `--use-owner-token`, the task will run with the service account's access rules, so make 
   sure the account uses resources it has access to
 :::