diff --git a/content/change-logs/analytics/cumulocity-undefined-notifications-tenant-context-operations-wildcard.md b/content/change-logs/analytics/cumulocity-undefined-notifications-tenant-context-operations-wildcard.md
new file mode 100644
index 0000000000..cfd490fe41
--- /dev/null
+++ b/content/change-logs/analytics/cumulocity-undefined-notifications-tenant-context-operations-wildcard.md
@@ -0,0 +1,18 @@
+---
+date:
+title: Changes to Notifications 2.0 tenant context subscriptions with no API filter
+change_type:
+  - value: change-3BQrQ6adS
+    label: API change
+product_area: Platform services
+component:
+  - value: component-JlFdtOPva
+    label: REST API
+build_artifact:
+  - value: tc-QHwMfWtBk7
+    label: cumulocity
+ticket: MTM-60734
+version: 2025.30.0
+---
+
+As previously [announced](https://cumulocity.com/docs/change-logs/?change-type=.change-type-api-change#cumulocity-undefined-notifications-tenant-context-operations-wildcard-announcement), applications utilizing the wildcard API selector in Notifications 2.0 tenant context subscriptions will now start receiving operations updates in addition to the updates they were already receiving. This change applies to both existing and new tenant context subscriptions.
\ No newline at end of file
diff --git a/content/change-logs/platform-services/cumulocity-undefined-notifications-tenant-context-event-type-filter.md b/content/change-logs/platform-services/cumulocity-undefined-notifications-tenant-context-event-type-filter.md
new file mode 100644
index 0000000000..e21315b029
--- /dev/null
+++ b/content/change-logs/platform-services/cumulocity-undefined-notifications-tenant-context-event-type-filter.md
@@ -0,0 +1,20 @@
+---
+date:
+title: Changes to Notifications 2.0 tenant context subscriptions with event API filter
+change_type:
+  - value: change-QHu1GdukP
+    label: Feature
+product_area: Platform services
+component:
+  - value: component-JlFdtOPva
+    label: REST API
+build_artifact:
+  - value: tc-QHwMfWtBk7
+    label: cumulocity
+ticket: MTM-60734
+version: 2025.30.0
+---
+
+Notifications 2.0 subscriptions may specify the {{< product-c8y-iot >}} APIs to subscribe to, for example `events` or `measurements`.
+If the `events` API was specifically included as the only API in a tenant context subscription filter, a type filter was also required to be set in that filter to make the subscription work.
+The restriction requiring a type filter when subscribing to the `events` API in the tenant context has been removed. Tenant context subscriptions to the `events` API can now be created without specifying a type filter.
\ No newline at end of file