diff --git a/docs/sources/configuration/_index.md b/docs/sources/configuration/_index.md
index 060c2901fcfd3..423aa256bccb3 100644
--- a/docs/sources/configuration/_index.md
+++ b/docs/sources/configuration/_index.md
@@ -2384,10 +2384,6 @@ The `limits_config` block configures global and per-tenant limits in Loki.
 # This also determines how cache keys are chosen when result caching is enabled
 # CLI flag: -querier.split-queries-by-interval
 [split_queries_by_interval: <duration> | default = 30m]
-
-# When true, access to the deletion API is enabled.
-# CLI flag: -compactor.allow_deletes
-[allow_deletes: <boolean> | default = false]
 ```
 
 ## sigv4_config
diff --git a/docs/sources/operations/storage/logs-deletion.md b/docs/sources/operations/storage/logs-deletion.md
index 11723963ee6f0..9e58b27b1f556 100644
--- a/docs/sources/operations/storage/logs-deletion.md
+++ b/docs/sources/operations/storage/logs-deletion.md
@@ -28,4 +28,4 @@ With `filter-and-delete`, log lines matching the query in the delete request are
 
 A delete request may be canceled within a configurable cancellation period. Set the `delete_request_cancel_period` in the compactor's YAML configuration or on the command line when invoking Loki. Its default value is 24h.
 
-Access to the deletion API can be enabled per tenant via the `allow_deletes` setting.
+As long as the `compactor.retention_enabled` setting is `true`, the API endpoints will be available. Afterwards, access to the deletion API can be enabled per tenant via the `deletion_mode` tenant override.