Adding clarity around 'tenant scope'

mooreds · mooreds · commit 33515f1cd6aa · 2022-06-17T07:22:36.000-06:00
diff --git a/site/docs/v1/tech/events-webhooks/_tenant-or-application-scoped-event.adoc b/site/docs/v1/tech/events-webhooks/_tenant-or-application-scoped-event.adoc
@@ -1,3 +1,3 @@
-This is a tenant or application scoped event. It can be sent to all applications in a tenant or to one or more specified applications.
+This is a tenant or application scoped event. It can be sent to all applications in a tenant or to one or more specified applications. It will also be sent to all tenants that are listening for this event. A [field]#tenantId# will be present in the payload to allow for filtering.
 
-The ability to limit the generation of an event for only certain applications is legacy functionality and may be modified in the future. You almost certainly want to enable this event at the tenant level and optionally filter on the `applicationId` when consuming the event.
+The ability to limit the generation of an event for only certain applications is legacy functionality and may be modified in the future. You almost certainly want to enable this event at the tenant level and optionally filter on the [field]#applicationId# when consuming the event.
diff --git a/site/docs/v1/tech/events-webhooks/_tenant-scoped-event.adoc b/site/docs/v1/tech/events-webhooks/_tenant-scoped-event.adoc
@@ -1 +1 @@
-This is a tenant scoped event.
+This is a tenant scoped event. This event will be sent to all tenants that are listening, but will contain a [field]#tenantId# to allow for filtering.

Original file line number	Diff line number	Diff line change
`@@ -1 +1 @@`
`1`		`-This is a tenant scoped event.`
	`1`	`+This is a tenant scoped event. This event will be sent to all tenants that are listening, but will contain a [field]#tenantId# to allow for filtering.`