diff --git a/docs/codacy-guardrails/codacy-guardrails-getting-started.md b/docs/codacy-guardrails/codacy-guardrails-getting-started.md
index d4ed2c259f..8189c86512 100644
--- a/docs/codacy-guardrails/codacy-guardrails-getting-started.md
+++ b/docs/codacy-guardrails/codacy-guardrails-getting-started.md
@@ -224,6 +224,16 @@ c. Open the Copilot chat and switch the mode to `Agent`. You can check that the
 
 ![Copilot Agent with Codacy tools](images/copilot_agent.png)
 
+## Proxy configuration
+
+Codacy Guardrails supports working behind a proxy. To set it up, configure your proxy the same way you would for any other VSCode feature, either through the IDE settings or through your system's environment variables.
+
+### CA certificate path
+
+If your proxy uses a custom CA certificate, the extension has an extra setting as a fallback option to add the path of the certificate: **Codacy › Proxy: CA Cert Path** (`codacy.proxy.caCertPath`).
+
+![Codacy proxy CA certificate path setting](images/codacy-proxy-ca-cert-path.png)
+
 
 # JetBrains IDEs
 
diff --git a/docs/codacy-guardrails/images/codacy-proxy-ca-cert-path.png b/docs/codacy-guardrails/images/codacy-proxy-ca-cert-path.png
new file mode 100644
index 0000000000..8ca160e1c0
Binary files /dev/null and b/docs/codacy-guardrails/images/codacy-proxy-ca-cert-path.png differ