diff --git a/content/kubermatic/main/architecture/iam-role-based-access-control/_index.en.md b/content/kubermatic/main/architecture/iam-role-based-access-control/_index.en.md
index 8719ec556..daa995ccf 100644
--- a/content/kubermatic/main/architecture/iam-role-based-access-control/_index.en.md
+++ b/content/kubermatic/main/architecture/iam-role-based-access-control/_index.en.md
@@ -48,8 +48,28 @@ dex:
 
 And apply the changes to the cluster:
 
+
+> **Note – Multiple Helm values files**  
+> The `kubermatic-installer` accepts **multiple** Helm values files by **repeating** the `--helm-values` flag:
+> 
+> ```bash
+> ./kubermatic-installer deploy <stack> \
+>   --config kubermatic.yaml \
+>   --helm-values values/defaults.yaml \
+>   --helm-values values/<env>.yaml \
+>   --helm-values values/secrets.yaml
+> ```
+> 
+> **Order matters:** Later files **override** earlier ones. Maps are merged recursively, **lists are replaced** (Helm semantics).  
+> The legacy single-file input remains supported for backward compatibility.
+
+
 ```bash
-./kubermatic-installer deploy --config kubermatic.yaml --helm-values values.yaml
+./kubermatic-installer deploy \
+  --config kubermatic.yaml \
+  --helm-values values/defaults.yaml \
+  --helm-values values/dex.yaml \
+  --helm-values values/secrets.yaml
 ```
 
 ## Authorization
diff --git a/content/kubermatic/main/installation/install-kkp-ce/_index.en.md b/content/kubermatic/main/installation/install-kkp-ce/_index.en.md
index 2e8afcbb6..ba75360f5 100644
--- a/content/kubermatic/main/installation/install-kkp-ce/_index.en.md
+++ b/content/kubermatic/main/installation/install-kkp-ce/_index.en.md
@@ -148,8 +148,26 @@ mentioned above can be generated using any password generator or on the shell us
 Kubermatic Installer will suggest some properly generated secrets for you when it
 notices that some are missing, for example:
 
+> **Note – Multiple Helm values files**  
+> The `kubermatic-installer` accepts **multiple** Helm values files by **repeating** the `--helm-values` flag:
+> 
+> ```bash
+> ./kubermatic-installer deploy <stack> \
+>   --config kubermatic.yaml \
+>   --helm-values values/defaults.yaml \
+>   --helm-values values/<env>.yaml \
+>   --helm-values values/secrets.yaml
+> ```
+> 
+> **Order matters:** Later files **override** earlier ones. Maps are merged recursively, **lists are replaced** (Helm semantics).  
+> The legacy single-file input remains supported for backward compatibility.
+
 ```bash
-./kubermatic-installer deploy --config kubermatic.yaml --helm-values values.yaml
+./kubermatic-installer deploy \
+  --config kubermatic.yaml \
+  --helm-values values/defaults.yaml \
+  --helm-values values/prod.yaml \
+  --helm-values values/secrets.yaml
 ```
 
 Output will be similar to this:
@@ -276,6 +294,7 @@ like so:
   # --storageclass aws \
   --config kubermatic.yaml \
   --helm-values values.yaml
+  # If necessary, add additional --helm-values, see note above.
 ```
 
 {{% notice warning %}}
diff --git a/content/kubermatic/main/installation/install-kkp-ce/add-seed-cluster/_index.en.md b/content/kubermatic/main/installation/install-kkp-ce/add-seed-cluster/_index.en.md
index 52cc68ae9..609b50b13 100644
--- a/content/kubermatic/main/installation/install-kkp-ce/add-seed-cluster/_index.en.md
+++ b/content/kubermatic/main/installation/install-kkp-ce/add-seed-cluster/_index.en.md
@@ -212,13 +212,30 @@ a suitable `StorageClass` and is therefore still recommended to use.
 Similar to how the Master Cluster can be installed with the installer, run the `deploy kubermatic-seed` command. You still need to
 manually ensure that the StorageClass you configured for MinIO exists already.
 
+> **Note – Multiple Helm values files**  
+> The `kubermatic-installer` accepts **multiple** Helm values files by **repeating** the `--helm-values` flag:
+> 
+> ```bash
+> ./kubermatic-installer deploy <stack> \
+>   --config kubermatic.yaml \
+>   --helm-values values/defaults.yaml \
+>   --helm-values values/<env>.yaml \
+>   --helm-values values/secrets.yaml
+> ```
+> 
+> **Order matters:** Later files **override** earlier ones. Maps are merged recursively, **lists are replaced** (Helm semantics).  
+> The legacy single-file input remains supported for backward compatibility.
+
 ```bash
 export KUBECONFIG=/path/to/seed-cluster/kubeconfig
 ./kubermatic-installer deploy kubermatic-seed \
   # uncomment the line below after updating it to your respective provider; remove flag if provider is not supported or cluster is shared with master (see above)
   # --storageclass aws \
   --config kubermatic.yaml \
-  --helm-values values.yaml
+  --helm-values values/defaults.yaml \
+  --helm-values values/seed.yaml \
+  --helm-values values/secrets.yaml
+
 ```
 
 The command above will take care of installing/updating the CRDs, setting up MinIO and the S3-exporter and attempts
diff --git a/content/kubermatic/main/tutorials-howtos/monitoring-logging-alerting/master-seed/installation/_index.en.md b/content/kubermatic/main/tutorials-howtos/monitoring-logging-alerting/master-seed/installation/_index.en.md
index 6818bc4b6..22029149d 100644
--- a/content/kubermatic/main/tutorials-howtos/monitoring-logging-alerting/master-seed/installation/_index.en.md
+++ b/content/kubermatic/main/tutorials-howtos/monitoring-logging-alerting/master-seed/installation/_index.en.md
@@ -123,8 +123,25 @@ With this file prepared, we can now install all required charts:
 
 **Kubermatic Installer**
 
+> **Note – Multiple Helm values files**  
+> The `kubermatic-installer` accepts **multiple** Helm values files by **repeating** the `--helm-values` flag:
+> 
+> ```bash
+> ./kubermatic-installer deploy <stack> \
+>   --config kubermatic.yaml \
+>   --helm-values values/defaults.yaml \
+>   --helm-values values/<env>.yaml \
+>   --helm-values values/secrets.yaml
+> ```
+> 
+> **Order matters:** Later files **override** earlier ones. Maps are merged recursively, **lists are replaced** (Helm semantics).  
+> The legacy single-file input remains supported for backward compatibility.
+
 ```bash
-./kubermatic-installer deploy seed-mla --helm-values values.yaml
+./kubermatic-installer deploy seed-mla \
+  --helm-values values/defaults.yaml \
+  --helm-values values/seed-mla.yaml \
+  --helm-values values/secrets.yaml
 ```
 
 Output will be similar to this:
diff --git a/content/kubermatic/main/tutorials-howtos/monitoring-logging-alerting/user-cluster/admin-guide/_index.en.md b/content/kubermatic/main/tutorials-howtos/monitoring-logging-alerting/user-cluster/admin-guide/_index.en.md
index 928551dbf..10f471a19 100644
--- a/content/kubermatic/main/tutorials-howtos/monitoring-logging-alerting/user-cluster/admin-guide/_index.en.md
+++ b/content/kubermatic/main/tutorials-howtos/monitoring-logging-alerting/user-cluster/admin-guide/_index.en.md
@@ -53,8 +53,26 @@ Other parameters which can become important if you have particularly high values
 
 The MLA stack can be deployed by using the Kubermatic Installer:
 
+> **Note – Multiple Helm values files**  
+> The `kubermatic-installer` accepts **multiple** Helm values files by **repeating** the `--helm-values` flag:
+> 
+> ```bash
+> ./kubermatic-installer deploy <stack> \
+>   --config kubermatic.yaml \
+>   --helm-values values/defaults.yaml \
+>   --helm-values values/<env>.yaml \
+>   --helm-values values/secrets.yaml
+> ```
+> 
+> **Order matters:** Later files **override** earlier ones. Maps are merged recursively, **lists are replaced** (Helm semantics).  
+> The legacy single-file input remains supported for backward compatibility.
+
 ```bash
-kubermatic-installer deploy usercluster-mla --config <kubermatic.yaml> --helm-values <mlavalues.yaml>
+kubermatic-installer deploy usercluster-mla \
+  --config kubermatic.yaml \
+  --helm-values values/defaults.yaml \
+  --helm-values values/mla.yaml \
+  --helm-values values/secrets.yaml
 ```
 
 Additional options that can be used for the installation include:
@@ -118,6 +136,7 @@ dex:
 At this point, we can install the IAP Helm chart into the mla namespace as follows:
 
 ```bash
+# If necessary, add additional --helm-values, see note above.
 kubermatic-installer deploy usercluster-mla --config <kubermatic.yaml> --helm-values <mlavalues.yaml> --mla-include-iap
 ```
 
@@ -507,5 +526,6 @@ kubectl delete svc cortex-store-gateway -n mla
 After doing the above-mentioned steps, MLA stack can be upgraded using the Kubermatic Installer:
 
 ```bash
+# If necessary, add additional --helm-values, see note above.
 kubermatic-installer deploy usercluster-mla --config <kubermatic.yaml> --helm-values <mlavalues.yaml>
 ```
diff --git a/content/kubermatic/main/tutorials-howtos/telemetry/_index.en.md b/content/kubermatic/main/tutorials-howtos/telemetry/_index.en.md
index 35ee7dc16..90899ef5b 100644
--- a/content/kubermatic/main/tutorials-howtos/telemetry/_index.en.md
+++ b/content/kubermatic/main/tutorials-howtos/telemetry/_index.en.md
@@ -31,8 +31,26 @@ The `schedule` is in Cron format, please check [Cron format](https://en.wikipedi
 
 Then you can use the Kubermatic installer to install KKP by using the following command:
 
+> **Note – Multiple Helm values files**  
+> The `kubermatic-installer` accepts **multiple** Helm values files by **repeating** the `--helm-values` flag:
+> 
+> ```bash
+> ./kubermatic-installer deploy <stack> \
+>   --config kubermatic.yaml \
+>   --helm-values values/defaults.yaml \
+>   --helm-values values/<env>.yaml \
+>   --helm-values values/secrets.yaml
+> ```
+> 
+> **Order matters:** Later files **override** earlier ones. Maps are merged recursively, **lists are replaced** (Helm semantics).  
+> The legacy single-file input remains supported for backward compatibility.
+
 ```bash
-./kubermatic-installer deploy --config kubermatic.yaml --helm-values values.yaml
+./kubermatic-installer deploy \
+  --config kubermatic.yaml \
+  --helm-values values/defaults.yaml \
+  --helm-values values/telemetry.yaml \
+  --helm-values values/secrets.yaml
 ```
 
 After this command finishes, a CronJob will be created in the `telemetry-system` namespace on the master cluster. The CronJob includes the following components:
@@ -53,7 +71,12 @@ helm --namespace telemetry-system upgrade --atomic --create-namespace --install
 If you don’t want to send usage data to us to improve our product, or your KKP will be running in offline mode which doesn’t have access to the public Telemetry endpoint, you can disable it by using `--disable-telemetry` flag as following:
 
 ```bash
-./kubermatic-installer deploy --disable-telemetry --config kubermatic.yaml --helm-values values.yaml
+./kubermatic-installer deploy \
+  --disable-telemetry \
+  --config kubermatic.yaml \
+  --helm-values values/defaults.yaml \
+  --helm-values values/telemetry.yaml \
+  --helm-values values/secrets.yaml
 ```
 
 ## Data that Telemetry Collects