diff --git a/docs/remote_config.md b/docs/remote_config.md
new file mode 100644
index 000000000..6796c76e5
--- /dev/null
+++ b/docs/remote_config.md
@@ -0,0 +1,40 @@
+# Remote Configuration (beta)
+
+This feature was introduced in Datadog Operator v1.7.0 and is currently in beta.
+
+## Overview
+
+Remote Configuration in the Datadog Operator allows you to enable features in a Kubernetes cluster from Datadog.
+
+You can create a policy on the Fleet Automation page to enable a feature for an eligible scope. The Datadog Operator then updates the Agents with the necessary configuration.
+
+## Prerequisites
+
+* Datadog Operator v1.7.0+
+
+## Enabling Remote Configuration
+
+Remote Configuration is disabled by default. To enable it using the latest [datadog-operator Helm chart](https://github.com/DataDog/helm-charts/tree/main/charts/datadog-operator), create a Kubernetes Secret that contains your API and application keys:
+
+```shell
+export DD_API_KEY=<YOUR_API_KEY>
+export DD_APP_KEY=<YOUR_APP_KEY>
+
+kubectl create secret generic datadog-operator-secret --from-literal api-key=$DD_API_KEY --from-literal app-key=$DD_APP_KEY
+```
+
+Then modify your `values.yaml` file with the following:
+
+```yaml
+clusterName: example-cluster-name
+remoteConfiguration:
+  enabled: true
+apiKeyExistingSecret: datadog-operator-secret
+appKeyExistingSecret: datadog-operator-secret
+```
+
+Then install the Datadog Operator:
+
+```shell
+helm install my-datadog-operator datadog/datadog-operator -f values.yaml
+```