Incorrect notification delivery

Flinn sends notifications about searches, documents and activities across modules (M1, M2, M4). If notification delivery is not correctly scoped to a user's access rights, a user could receive alerts about content they are not permitted to access — or miss alerts they are entitled to — which could disclose confidential search configurations or regulatory activity, or cause confusion and incorrect actions.

Hazardous situation: A user receives notifications about searches, documents or activities they cannot access, or fails to receive notifications they are legitimately entitled to.

• Permission-aware delivery. Notification delivery is governed server-side by the user's access rights; the system checks the user's permission state at dispatch so that only authorised users receive alerts. See Roles & Permissions.
• Full traceability. Notification delivery events are recorded in the activity log, enabling detection and review of any incorrect dispatch; see Audit Trail.
• Report anomalies. If you receive alerts for content you cannot access — or miss alerts you expect — Report a problem or a bug.

Timely, permission-aware notifications outweigh the residual risk of a dispatch error, which is detectable via the activity log and correctable without data loss.

Related: Incorrect user permission enforcement, Privilege escalation, Data breach.