diff --git a/content/en/docs/Installation/installation-guide/install-with-helm.md b/content/en/docs/Installation/installation-guide/install-with-helm.md
index ade0b793..38422cc7 100644
--- a/content/en/docs/Installation/installation-guide/install-with-helm.md
+++ b/content/en/docs/Installation/installation-guide/install-with-helm.md
@@ -69,6 +69,7 @@ command:
 $ helm install \
     --set cr.create=true \
     --set cr.namespace=istio-system \
+    --set cr.auth.strategy="anonymous" \
     --namespace kiali-operator \
     --create-namespace \
     kiali-operator \
@@ -80,7 +81,10 @@ create the `kiali-operator` namespace (if needed), and deploy the Kiali
 operator on it.  The `--set cr.create=true` and `--set
 cr.namespace=istio-system` flags instructs to create a Kiali CR in the
 `istio-system` namespace. Since the Kiali CR is created in advance, as soon as
-the Kiali operator starts, it will process it to deploy Kiali.
+the Kiali operator starts, it will process it to deploy Kiali. After Kiali has started,
+you can access Kiali UI through 'http://localhost:20001' by executing 
+`kubectl port-forward service/kiali -n istio-system 20001:20001`
+because of `--set cr.auth.strategy="anonymous"`. But realize that anonymous mode will allow anyone to be able to see and use Kiali. If you wish to require users to authenticate themselves by logging into Kiali, use one of the other [auth strategies](/docs/configuration/authentication/).
 
 The Kiali Operator Helm Chart is configurable. Check available options and default values by running: