diff --git a/content/docs/2.15/operate/events.md b/content/docs/2.15/operate/events.md
index a4bf08ff1..70ed9cb36 100644
--- a/content/docs/2.15/operate/events.md
+++ b/content/docs/2.15/operate/events.md
@@ -79,6 +79,21 @@ In general, an event emitted by KEDA would fundamentally come down to the follow
 }
 ```
 
+### Scopes: Namespace vs. Cluster
+
+Each `CloudEventSource` is defined in one namespace. For cases where you want to share a single sink among many namespaces, you can instead create a `ClusterCloudEventSource`. As a global object, this can be used from any namespace. 
+
+Defining a `ClusterCloudEventSource` works almost identically to a `CloudEventSource`, except there is no `metadata.namespace` value:
+
+```yaml
+apiVersion: keda.sh/v1alpha1
+kind: ClusterCloudEventSource
+metadata:
+  name: {cluster-cloudeventsource-name}
+spec:
+  # As before ...
+```
+
 ### Event Sinks
 
 There will be multiple types of destination to emit KEDA events to.