devdocs/specs/core-notification.txt

@@ -2,6 +2,7 @@
 
 Important cases:
 client viewing ui (was popup in v7)	https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/3783
+Restrict to involved people only: https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/892
 
 
 ALL EVENT TYPES INITIAL RELEASE
@@ -29,7 +30,7 @@ WorkOrderStatusAge "deadman" delivery if not changed before XX time period
 	also quote maybe?
 UnitWarranyExpiry case 1361
 UnitMeterReadingMultipleExceeded case 1254
-	
+
 
 Not for certain but in the hopper to think about:
 On demand ad-hoc notification case 3466 for specific object only
@@ -63,6 +64,8 @@ One enum list of NotificationType for any possible notification that can be proc
 	Notify type is divided by actual type and then by actual delivery method
 No delivery schedule anymore, let user decide how to handle at their device end, not our concern, just deliver immediately always
 Notify BEfore shoudl support multiple time frames, not just one
+Users not involved should not be notified, have choice on that`
+	e.g. if a user is not booked on a workorder and is just a lowly tech they don't care about other workorder status changes
 
 Types of notifications sitting in delivery queue:
 	Deliver if something not changed before date "DEADMAN SWITCH"