diff --git a/README.md b/README.md
index 7ae6df0..524e09c 100644
--- a/README.md
+++ b/README.md
@@ -67,19 +67,26 @@ Note that you can optionally set environment variables to override the default b
*(Here, the simple, automatic method is described. Besides the automatic method, you can also generate the keys [manually](docs/manually_gen_key.md).)*
+**Security Recommendation:** We recommend using the **Charging Manager** role for security. It provides limited access suitable for charging management and works perfectly with [evcc tesla-ble template](https://docs.evcc.io/docs/devices/vehicles#tesla-ble). The Charging Manager role can:
+- Read vehicle data
+- Authorize charging-related commands: `wake`, `charge_start`, `charge_stop`, `set_charging_amps`
+
+The **Owner** role provides full access to all vehicle functions (unlock, start, etc.) and should only be used if you need non-charging functions.
+
To generate the required keys browse to `http://YOUR_IP:8080/dashboard`. In the dashboard you will see that the keys are missing:
-
+
-Please click on `generate Keys` and the keys will be automatically generated and saved.
+Please click on `Generate` for the **Charging Manager** role (recommended for security). The keys will be automatically generated and saved. The Charging Manager key will be set as active by default.
-
+
+
After that please enter your VIN under `Setup Vehicle`. Before you proceed make sure your vehicle is awake! So you have to manually wake the vehicle before you send the key to the vehicle.
-
+
-Finally the keys is send to the vehicle. You have to confirm by tapping your NFC card on center console.
+The key is now sent to the vehicle. To complete the process, confirm by tapping your NFC card on the center console. (Note: There will be no message on the Tesla screen before confirmation with the NFC card.)
diff --git a/docs/installation.md b/docs/installation.md
index bc4934b..45fdd26 100644
--- a/docs/installation.md
+++ b/docs/installation.md
@@ -114,19 +114,26 @@ This variant will be described later.
## Step 3: Generate key for vehicle
+**Security Recommendation:** We recommend using the **Charging Manager** role for security. It provides limited access suitable for charging management and works perfectly with [evcc tesla-ble template](https://docs.evcc.io/docs/devices/vehicles#tesla-ble). The Charging Manager role can:
+- Read vehicle data
+- Authorize charging-related commands: `wake`, `charge_start`, `charge_stop`, `set_charging_amps`
+
+The **Owner** role provides full access to all vehicle functions (unlock, start, etc.) and should only be used if you need non-charging functions.
+
To generate the required keys browse to `http://YOUR_IP:8080/dashboard`. In the dashboard you will see that the keys are missing:
-
+
-Please click on `generate Keys` and the keys will be automatically generated and saved.
+Please click on `Generate` for the **Charging Manager** role (recommended for security). The keys will be automatically generated and saved. The Charging Manager key will be set as active by default.
-
+
+
After that please enter your VIN under `Setup Vehicle`. Before you proceed make sure your vehicle is awake! So you have to manually wake the vehicle before you send the key to the vehicle.
-
+
-Finally the keys is send to the vehicle. You have to confirm by tapping your NFC card on center console.
+The key is now sent to the vehicle. To complete the process, confirm by tapping your NFC card on the center console. (Note: There will be no message on the Tesla screen before confirmation with the NFC card.)
diff --git a/docs/proxy1.png b/docs/proxy1.png
index 387e109..e3611cf 100644
Binary files a/docs/proxy1.png and b/docs/proxy1.png differ
diff --git a/docs/proxy2.png b/docs/proxy2.png
index 5493e4c..bfb3ab6 100644
Binary files a/docs/proxy2.png and b/docs/proxy2.png differ
diff --git a/docs/proxy2b.png b/docs/proxy2b.png
new file mode 100644
index 0000000..d20b244
Binary files /dev/null and b/docs/proxy2b.png differ
diff --git a/docs/proxy3.png b/docs/proxy3.png
index 0ef6409..770b45b 100644
Binary files a/docs/proxy3.png and b/docs/proxy3.png differ
diff --git a/docs/proxy6.png b/docs/proxy6.png
index e55e5e2..f0ed397 100644
Binary files a/docs/proxy6.png and b/docs/proxy6.png differ
diff --git a/docs/proxy7.png b/docs/proxy7.png
deleted file mode 100644
index 60ce1e9..0000000
Binary files a/docs/proxy7.png and /dev/null differ