diff --git a/docs-data/property-overrides.json b/docs-data/property-overrides.json
index 0f9dcc3da3..63ced84665 100644
--- a/docs-data/property-overrides.json
+++ b/docs-data/property-overrides.json
@@ -2133,6 +2133,16 @@
       ],
       "config_scope": "cluster",
       "description": "The default write caching mode to apply to user topics. Write caching acknowledges a message as soon as it is received and acknowledged on a majority of brokers, without waiting for it to be written to disk. With `acks=all`, this provides lower latency while still ensuring that a majority of brokers acknowledge the write. \n\nFsyncs follow <<raft_replica_max_pending_flush_bytes,`raft_replica_max_pending_flush_bytes`>> and <<raft_replica_max_flush_delay_ms,`raft_replica_max_flush_delay_ms`>>, whichever is reached first.\n\nThe `write_caching_default` cluster property can be overridden with the xref:reference:properties/topic-properties.adoc#writecaching[`write.caching`] topic property."
+    },
+    "delete_topic_enable": {
+      "type": "boolean",
+      "default": true,
+      "description": "Controls whether topics can be deleted through the Kafka DeleteTopics API. When set to `false`, all topic deletion requests are rejected for all users, including superusers. Use this as a cluster-wide safety setting to prevent accidental topic deletion in production environments.\n\nFor per-topic deletion protection, see xref:reference:properties/cluster-properties.adoc#kafka_nodelete_topics[`kafka_nodelete_topics`].",
+      "related_topics": [
+        "xref:reference:properties/cluster-properties.adoc#kafka_nodelete_topics[`kafka_nodelete_topics`]",
+        "xref:get-started:licensing/index.adoc[enterprise license]"
+      ],
+      "config_scope": "cluster"
     }
   }
 }
diff --git a/modules/get-started/pages/licensing/overview.adoc b/modules/get-started/pages/licensing/overview.adoc
index 93d0a73edc..0fdead3df2 100644
--- a/modules/get-started/pages/licensing/overview.adoc
+++ b/modules/get-started/pages/licensing/overview.adoc
@@ -88,7 +88,7 @@ IMPORTANT: To avoid startup issues with Redpanda Console when a trial or Enterpr
 - **Redpanda Connect**: To evaluate enterprise features in Redpanda Connect, you must xref:redpanda-connect:get-started:licensing.adoc#apply-a-license-key-to-redpanda-connect[apply a trial license key]. After the 30-day evaluation period, you are blocked from using enterprise connectors unless you https://www.redpanda.com/upgrade[upgrade to an Enterprise Edition license^].
 
 [[self-managed]]
-=== Redpanda enterprise features
+=== Redpanda Enterprise Edition features
 
 The following table lists the enterprise features for Redpanda and how Redpanda behaves upon license expiration when each enterprise feature is enabled.
 
@@ -136,7 +136,7 @@ Continuous Intra-Broker Partition Balancing is enabled by default for all new cl
 | Provides secure Kerberos-based authentication.
 | No change.
 
-| xref:manage:security/authentication.adoc#kerberos[Leader Pinning]
+| xref:develop:produce-data/leader-pinning.adoc[Leader Pinning]
 | Specifies the set of availability zones where the leaders of partitions of a given topic should be located.
 | Leader Pinning is disabled on all topics.
 
@@ -164,6 +164,10 @@ Continuous Intra-Broker Partition Balancing is enabled by default for all new cl
 | Provides enterprise-grade disaster recovery through asynchronous, offset-preserving replication between distinct Redpanda clusters for cross-region data protection.
 | New shadow links cannot be created. Existing shadow links continue operating and can be updated.
 
+| Topic Deletion Control (`delete_topic_enable`)
+| When set to `false`, prevents all users, including superusers, from deleting topics through the Kafka DeleteTopics API. This property provides a cluster-wide safety guard against accidental topic deletion.
+| Topic deletion reverts to enabled (`true`).
+
 | xref:manage:topic-recovery.adoc[Topic Recovery]
 | Allows restoring a single topic from Tiered Storage using remote recovery properties.
 | You cannot create topics with the `redpanda.remote.recovery=true` property or perform topic recovery operations. To proceed, add a valid license to the target cluster. Without a valid license, topic recovery is blocked.