Per-Person Notification Preferences: Who Gets What Alert

Why notification fatigue is an expensive problem in HR

Notification preferences that aren't set up correctly turn a field and HR system into a noise machine before long. A site manager gets violation alerts for a site their team has nothing to do with. An HR manager drowns in a push notification for every single approval step in a chain they're only loosely involved in. An employee starts seeing company-wide announcements mixed into the same channel as their own shift reminders. The outcome is predictable: people learn to dismiss notifications without reading them, and the one that actually mattered gets lost in that habit.

This isn't a theoretical risk — it's wear and tear that every company running a field team eventually hits. Within a few weeks, the gap between "a system that announces everything" and "a system that announces nothing" disappears in practice, because both produce the same result: the important event goes unnoticed. The fix isn't sending fewer notifications. It's sending the right notification to the right person, and that only works once preferences can be set per person rather than for the whole account.

Six channels, one person: how preference actually works

Inside HR-Tech's field-tracking HR platform, every user's mobile profile carries six separate notification channels, and each one can be switched on or off individually. One channel covers out-of-site violations, another covers requests waiting for approval, another handles company-wide announcements, another runs internal messaging — each toggle stands on its own. An employee can keep shift reminders on while turning off a company-wide channel that doesn't concern them; a site manager might set the exact opposite.

The value sits in the fact that the channels don't depend on one another. What matters to an employee is simple: "tell me the moment I step outside during a shift." What matters to a manager is different: "tell me the instant anyone on my team leaves the site." Both needs get served at once, in the same system, without either one drowning out the other. If notification preference were a single on/off switch, either everyone would get everything, or a genuinely critical alert would end up buried inside a channel someone quietly turned off months ago.

What a typical setup looks like by role

In practice, four roles need very different things from notifications. A company administrator usually keeps every channel on, because their responsibility spans the whole organization. A site manager leaves violation and tracking-outage alerts on for their own site, but turns off messaging traffic from sites they don't manage to cut down on noise. An employee typically keeps their own leave status, public holidays and shift reminders on, and only opens the company-wide announcement channel during periods that genuinely concern them — year-end payroll, say.

The preferences aren't meant to be static, either. When a new site manager is assigned, or an employee moves to a different site, notification preferences need a second look — otherwise someone keeps getting alerts for a site they're no longer responsible for, or stops getting any for the one they just took on. That small bit of upkeep belongs alongside operational visibility practices like tracking field teams on a live map — visibility is only complete once the right alert actually reaches the right person at the right time.

The common shortcut: "everyone gets everything"

The most frequent mistake during setup is leaving every channel on for everyone by default, just to save a few minutes of configuration. In the short term it looks like the safe choice — nobody misses anything. Within a few weeks it produces the opposite effect: because everyone gets everything, no single notification carries any weight, phones buzz constantly, and people start clearing the notification panel without opening it. A genuine out-of-site violation becomes collateral damage of that habit.

The second common mistake is setting preferences once and never revisiting them. As a company grows, adds sites, and reshapes its org chart, notification needs shift with it. A preference set that was correct three months ago may now be routing the wrong alert to the wrong person. Notification preferences deserve the same periodic review as a personnel record or an approval flow — especially whenever the branch or department hierarchy changes.

The security and audit angle

Notification preferences aren't just a matter of comfort — they're part of a chain of accountability. Who got notified when an out-of-site violation happened matters the moment a dispute or an audit comes up. The answer to "who received this alert, and who ignored it" needs to be unambiguous, and that's only possible in a system where notifications are set per person and traceable. As we covered in why audit logs matter, the system's own record does the same work here: when a channel was switched on or off should leave a trace, so "I never got a notification" stops being a defense that stands on its own.

Practical steps for setting it up

A workable order to follow: first, list what actually counts as critical for each role — out-of-site violations, requests waiting on approval, official announcements, shift reminders. Then match each channel to the events that role genuinely needs to react to, keeping a clear line between "nice to know" and "needs a response." When a new employee joins, apply a default preference set based on their role automatically, but let them adjust it themselves from their mobile profile — nobody knows their own needs better than they do. Finally, whenever the company structure changes — a new branch, a site manager handover, a department merger — fold a notification-preference review into that same update instead of treating it as a separate task.

Team size matters here too. In a ten-person site where everyone already knows everyone, a loose notification setup might not cause real harm. In a team past fifty, that same looseness dilutes every single alert. As teams grow, setting role-based templates and treating individual overrides as the exception — rather than configuring preferences from scratch for every new hire — stays both faster and more consistent.

The takeaway

The cure for notification fatigue isn't a quieter system — it's a more precise one. When six channels can be switched on or off per person, every role gets the alerts that actually concern them, and the one that truly matters doesn't get lost in unnecessary traffic. If you want to review how your field team's notifications are set up, get in touch with the HR-Tech team — we can work out which channel should reach whom based on your actual role structure.