diff --git a/docs/content/asset_modelling/engagements_tests/PRO__organizations.md b/docs/content/asset_modelling/engagements_tests/PRO__organizations.md
index 7da9341e00..cc8af7884c 100644
--- a/docs/content/asset_modelling/engagements_tests/PRO__organizations.md
+++ b/docs/content/asset_modelling/engagements_tests/PRO__organizations.md
@@ -123,6 +123,13 @@ Findings) with the permissions that role grants. Pinning an Asset into an
 Organization therefore extends visibility, which is why creating a pin requires edit
 permission on **both** the Organization and the Asset.
 
+**Notifications follow the same rule.** Notifications about an Asset — and about its
+Engagements, Tests, and Findings — reach the members of every Organization the Asset
+belongs to, not only its primary one, subject as always to each user's own
+notification preferences. So pinning an Asset into a Compliance Scope Organization
+also makes that scope's members an audience for its findings, and removing the
+membership removes them again.
+
 ### Managing memberships
 
 - The Organization view gains a **Member Assets** table listing every member with