Per-identity filtering

Expanded Definition

Per-identity filtering is a recipient-specific ranking and routing control that evaluates email relevance against one user’s observed behaviour, not a shared tenant rule. In NHI and IAM-adjacent environments, that distinction matters because the control is usually driven by identity-linked telemetry, such as what a user opens, ignores, forwards, or searches for over time.

Where definitions vary across vendors is in how much automation is allowed before the control becomes a predictive model rather than a simple rules engine. NHI Management Group treats the term as a contextual decision layer that can improve signal quality, but it should still be governed as part of a broader identity and access posture, aligned with principles reflected in the NIST Cybersecurity Framework 2.0. The control is most useful when the recipient’s role, workflow, and communication pattern are stable enough to make per-person relevance meaningful.

The most common misapplication is using per-identity filtering as a substitute for access control, which occurs when organisations treat message ranking as if it were a security boundary.

Examples and Use Cases

Implementing per-identity filtering rigorously often introduces privacy and tuning overhead, requiring organisations to weigh sharper relevance against the cost of maintaining behavioural baselines and auditability.

• A finance analyst consistently receives payment approvals and vendor updates, so the filter surfaces those messages ahead of general announcements.
• A developer’s inbox prioritises CI/CD alerts and repository notifications, while low-value project broadcasts are pushed down unless the user previously engaged with them.
• An executive assistant sees travel, calendar, and delegation-related mail promoted because the system has learned that those messages are operationally urgent for that identity.
• A security operations user receives high-priority incident messages even if the sender is internal, because prior behaviour shows that timely review is critical for that account.
• As described in the Top 10 NHI Issues, visibility and control failures are common when identity context is not maintained; similar problems appear in email ranking when user-specific signals are not governed. For baseline identity guidance, the Ultimate Guide to NHIs is a useful reference point.

Why It Matters in NHI Security

Per-identity filtering matters because identity-scoped automation can either reduce noise or hide material signals, and in NHI-heavy environments the wrong message reaching the wrong workflow can delay human response to an active compromise. When organisations rely on identity-linked delivery logic, they need assurance that the logic does not suppress high-risk notices, credential warnings, or abnormal access events.

NHI Mgmt Group reports that only 5.7% of organisations have full visibility into their service accounts, which is a reminder that weak identity observability often extends beyond machine accounts into how messages and alerts are routed for humans and automation operators alike. That is why per-identity filtering should be evaluated alongside detection, routing, and escalation logic, not as a standalone productivity feature. The 52 NHI Breaches Analysis shows how quickly overlooked identity signals can compound into broader exposure when controls are fragmented.

Organisations typically encounter the cost of misrouted or suppressed identity-specific notifications only after an incident review, at which point per-identity filtering becomes operationally unavoidable to address.

Related resources from NHI Mgmt Group

• What is the difference between prompt filtering and identity governance for AI agents?
• Per-instance agent identity
• Per-Identity Behavioural Model
• What is a Non-Human Identity (NHI)?