diff --git a/java/cqn-services/remote-services.md b/java/cqn-services/remote-services.md
index a8e319a599..28e0bc9730 100644
--- a/java/cqn-services/remote-services.md
+++ b/java/cqn-services/remote-services.md
@@ -213,6 +213,38 @@ At runtime, this destination configuration will use the bound `identity` service
 
 [Learn more about consuming APIs from other IAS-Applications in the **SAP Cloud Identity Services documentation**.](https://help.sap.com/docs/cloud-identity-services/cloud-identity-services/consume-apis-from-other-applications){.learn-more}
 
+##### Configuring the Authentication Strategy {#ias-destination-authentication-strategy}
+
+By default, when calling a remote IAS-based API through a destination, CAP propagates the user identity associated with the current `RequestContext` (`currentUser`). If the user identity in the `RequestContext` is a named user, the named user will be propagated. If not, a technical user token will be requested.
+
+In some scenarios, especially for background processing or technical integrations, you may want to enforce the call to the remote API as a technical user instead. The `destination.onBehalfOf` configuration allows you to control this behavior:
+
+::: code-group
+```yaml [srv/src/main/resources/application.yaml]
+cds:
+  remote.services:
+    RemoteIasService:
+      destination:
+        name: my-ias-destination
+        onBehalfOf: systemUser
+```
+
+The following options are available:
+
+| Value | Description |
+|-------|-------------|
+| `currentUser` | Propagates the named user if available, or falls back to a tenant-specific technical user. **(default)** |
+| `systemUser` | Uses a tenant-specific technical user, based on the tenant set in the current Request Context. |
+| `systemUserProvider` | Uses a technical user of the provider tenant. Useful for internal communication that is not authorized tenant-specifically. |
+
+::: tip
+This behaves identically to the [`onBehalfOf` option in binding-based configurations](#configuring-the-authentication-strategy). Use it when your IAS app-2-app communication is configured via a BTP destination with `cloudsdk.ias-dependency-name` rather than a direct service binding.
+:::
+
+::: warning
+The `onBehalfOf` option only applies to IAS app-2-app destinations (destinations with the `cloudsdk.ias-dependency-name` property set). It has no effect on other destination types.
+:::
+
 #### Retrieve Destinations
 
 The CAP Java SDK obtains the destination for a _Remote Service_ from the `DestinationAccessor` using the name that is configured in the _Remote Service_'s destination configuration.