Alerts & Notifications

A number on a screen only helps if someone is looking at it. Alerts are what turn a zone into something that finds you — before you run dry, and before a delivery overfills a bay.

They arrive two ways:

• Email — in the inbox of whoever asked for it.
• In the portal — on the bell in the top bar.

The two are independent. Each person chooses which of them they want, for each site, and the choices are made in one place.

Where it lives

Open a site and choose Alerts in the header. That page — Alerts & notifications — holds the site’s rules and its recipient list together.

The site’s own page keeps the operational side: each zone shows its alert state where you are already looking at its number.

Alert rules

A rule is one zone, one metric, one threshold. Add as many as a zone needs.

Metric	Unit	Needs
Fill level	%	a capacity set on the zone
Days of material left	days	enough history to see a drawdown
Volume	m³ or ft³	—
Tonnage	t	a density on the zone

Each rule pairs that metric with a condition — Drops below or Rises above — and a number. Low fill and days-of-material rules are what stop you running out; a rises-above rule on fill level is what stops a delivery overfilling a bay.

The rule builder shows each zone’s current reading beside it, so you can set a threshold against what the zone actually reads today rather than guessing.

Note

Fill level rules need a capacity and tonnage rules need a density, both set on the zone. A metric the zone isn’t set up for is not offered. Days of material is a projection from observed consumption, so a brand-new zone won’t have one yet — see Days to empty is missing or doesn’t look right.

When a rule actually sends

A rule is in one of two states, ok or firing, and email goes out when the state changes — not on every scan while the condition is true. A zone that sits below its threshold for a week produces one email, not a thousand.

Three settings shape the rest:

• Reminder — how often to re-send while a rule stays firing. Don’t remind me (the default), every hour, every 6 hours, or every day. Use it for the rules somebody must act on.
• Email when resolved — a second email when the zone recovers. On by default.
• Recovery requires the value to clear the threshold by a margin rather than just touch it, so a number hovering on the line does not flap between firing and resolved.

Test a rule before you rely on it

Every rule has a Test button that sends the real email to you. Use it when you set a rule up — it confirms the address and the wording in one step, without waiting for a real threshold crossing.

Who gets notified

The Recipients card lists everyone with access to the site. A site notifies about two things, and each person answers one question about each:

	How you hear about it
Alerts — the threshold rules above	Email + portal · Email only · Portal only · Off
Deliveries — inbound loads, detected automatically from a rise in volume	Email + portal · Email only · Portal only · Off

Everyone with access starts on email + portal for both. So who hears about a zone is a per-person subscription rather than something set rule by rule — a new rule automatically reaches the people already subscribed.

The two are independent. Someone who wants alerts in their inbox but finds delivery mail noisy sets deliveries to Portal only and still sees every load when they look. Someone who lives in the portal all day sets both that way and never gets an email.

Admins see and manage the whole list. Everyone else sees only their own row, and sets their own two.

Send test delivery sends a sample delivery notification to you, which is the fastest way to confirm the list is right during a setup call. Alert rules have the equivalent Test button on each rule.

Unsubscribing from an email

Every alert and delivery email carries an unsubscribe link. One click drops that kind, for that site, for that person, from Email + portal to Portal only — it stops the mail and leaves the bell, so nothing is lost, it just stops arriving in an inbox. It does not affect anyone else, any other site, or the other kind. Set it back from the Alerts & notifications page.

Notifications in the portal

The bell in the top bar carries the same events as the email.

• An unread count sits on the bell, and new notifications arrive live without reloading the page.
• Opening one takes you to the zone it is about.
• Mark all read clears the count.
• Resolved notifications are marked apart from firing ones, so the list reads as a history rather than a to-do list.
• Notifications are kept for 90 days.

Tip

The bell is the channel to keep if you keep only one. It costs nobody an inbox, it holds its own 90-day history, and it is the one that is still there when somebody comes back from a week off.

A suggested setup

1. Start with one rule per zone that matters, on fill level if the zone has a capacity and on volume if it doesn’t. Enough to notice a problem, few enough to still be read.

2. Add days-of-material rules once the zone has history. They are the ones that give you time to order rather than time to react.

3. Set a reminder only on the rules somebody must act on. A reminder on everything trains people to ignore the mail.

4. Test each rule as you create it, and use Send test delivery once to confirm the recipient list.

5. Let people pick their own channels. Everyone controls their own two settings, so the fix for “too much mail” is switching to Portal only rather than being dropped from the list entirely.

6. Check the recipient list after people join or leave. Access decides who is on it, so a new team member is subscribed the moment they get access.

Team & AccessWho is on the recipient list is decided by who has access — invite people and set roles.

Troubleshooting & FAQA projection that looks wrong, a zone that stopped updating, and the other symptoms behind an alert.