Notification codes

Every row the system can write into your notification feed: the exact words you will read, what put the row there, who else received it, and where clicking it takes you.

Where: the bell at the top of the capsule → All notifications (/notifications); this is not a section, so it is not in the capsule list and no grant closes it. The bell and the page read the same feed under the same tabs — there is no second list to check.

Who can do what

Nobody chooses what they receive: there is no per-person notification setting. A row reaches you because of your role and because the section it belongs to is open to your group — see Roles & access.

At a glance

The feed of [Demo] Viewer — five system rows about invoices and five fleet alerts.

1. Quick views — All, Fleet, System, each with its unread count. Fleet and System are the two tabs the four kinds of row fall into, described below.
2. Unread only — hides everything you have already opened. Mark all read (top right) empties the badge without answering anything.
3. Row icon — the colour is the level, not the topic: grey-blue for info, amber for important, red for critical.
4. Open — follows the row's own link; the row is marked read on the way.

Key concepts

Four kinds of row, two tabs

Every row belongs to exactly one kind, and the kind decides which tab it lands on and what makes it go away. The split is by kind alone, never by subject — a to-do about the fleet still lands on System, because it is a to-do, not an alert.

Machine words come from the app, not from the database

A SYSTEM or ACTION row stores only a code (invoice_overdue) and the facts it needs (number, total, client). The sentence you read is assembled by the app from your own language. That is why the tables below list a code and a phrase with {placeholders}: the placeholders are filled in from the row, and the rest is translated.

Two consequences worth knowing: the same row reads in Arabic for a colleague who works in Arabic; and company data inside a row — item names, client names, ticket numbers — is never translated.

An announcement is the opposite: its words were typed by a person and are stored exactly as typed, in one language.

Level decides the shape, not the importance

A fleet alert never opens a window, however bad the finding is. A critical alert (CERT_EXPIRED) arrives as an important row: bold, counted, still just a line.

Read, acknowledged, closed

Three different states, and they are not interchangeable.

• Read — you saw the line. It clears the badge. Mark all read sets it on everything at once and answers nothing.
• Acknowledged — you pressed Got it. Only two things ask for it: an important or critical announcement (personal — your confirmation, not your colleague's) and a fleet alert (company-wide — one person acknowledges it for everyone, on the alert itself).
• Closed — the reason is gone. The row leaves the feed and the bell on its own.

Acknowledging a fleet alert does not close it. The finding is closed by data: renew the certificate and the row disappears by itself. Got it on an alert row needs Operator and above with the Alerts section — the steps are in Alerts.

Fleet and System, and the live reorder block

The bell panel and /notifications both carry the same two tabs beside All:

• Fleet — every alert row: the nightly rules' findings. Above the list sits Time to reorder, a live extra source: stock is counted at night but spent during the day, so this block asks the warehouse directly every 30 seconds and shows what is below minimum right now as {item} · {location} · {qty} < min {min}. A pair already covered by a STOCK_BELOW_MIN alert is shown as the alert instead, because the alert has a Got it.
• System — everything that is not an alert: announcements, your own to-dos (including "{count} items are not being depreciated"), and the system rows about invoices, repairs, tickets, imports and the ledger.

The bell panel shows the newest eight rows per tab and a link to All notifications; the page shows up to a hundred with counts on each tab.

Feed row, toast, email

The rule behind the split: you never get a feed row about your own action. Close a work order and your colleagues get the row; you get a toast. The full list of letters is in Email templates.

Fleet alert codes

Ten rules run nightly and write a row only when a finding is new — a certificate that has been expired for a week does not ring every morning. The row reads {item name} · {serial} on the first line and {rule} — {detail} on the second, and every one of them links to Alerts (/alerts).

Everyone whose group can see the Alerts section receives all ten.

Within a family the rules exclude each other: an item is either Certificate expiring or Certificate expired, never both. The daily summary of everything open arrives by email — see Alerts.

Announcement rows

Two sources, one shape. The row shows the title, a preview of the text, and who it is from: From {name}, From your workspace, or From the Hafrix team.

Announcements are written in Settings → Announcements — see Admin settings.

They are not edited after publishing — half the company has already read them. The author revokes the old one and writes a new one; revoking clears the row from everyone's list and stops the window from opening again, and what people have already read stays read.

To-do codes

Three, and each closes itself the moment its reason is gone. The first two are re-checked every minute while the app is open.

finance_no_policy is a to-do about equipment, but the split is by kind, not by subject: as an ACTION row it sits on the System tab like every other to-do.

System codes

Nineteen codes. Unless a row says otherwise, it goes to everyone who is Manager or above and whose group can see the section named in the last column — and never to the person who caused it.

Equipment and the yard

Repairs

An internal repair is silent: there is nothing to bill, and the item's own timeline already records it.

Field tickets

The two rejection rows are personal: in a batch of thirty, each author gets only their own.

Invoices

The ledger

All five go to Manager and above with the Finance section. The ledger rows are the one family that reaches everybody who qualifies, including the person who started the posting: a monthly close is not anybody's personal click.

The workspace

How to

Read the feed

Who: anyone.

1. Open the capsule and click the bell. The panel shows the eight most recent rows on three tabs.
2. Click a row to follow it — the row is marked read on the way.
3. For the whole list with counts and the unread filter, click All notifications.

Result: the badge drops by the rows you opened.

If it fails: an empty panel says Nothing new — you have no live rows, which is the normal state.

Clear the badge

Who: anyone.

1. Click Mark all read — in the bell panel or in the top right of /notifications.

Result: the badge and the tab counts go to zero. The rows stay in the list.

If it fails: nothing to clear — the button is off when the count is zero. Note that this answers nothing: an announcement still waits for Got it, an alert still waits for somebody to acknowledge it, and a to-do still waits for you to do it.

Confirm an announcement

Who: anyone.

1. An important or critical announcement opens in the middle of the screen, one at a time, oldest first. {count} more waiting tells you how many follow.
2. Read it and click Got it.

Result: the window closes and does not come back; the row is marked read. The next announcement, if any, opens.

If it fails: on a critical announcement Esc and a click outside do nothing — the button is the only way out. That is deliberate.

Find a row that has already closed

Who: anyone.

Closed rows are not shown anywhere in the feed — that is what closing means. What you are looking for is in the section the row came from:

1. A fleet alert → Alerts → the Closed quick view.
2. An announcement → Settings → Announcements, where the author sees it marked Revoked.
3. Anything else → the section itself: the invoice, the work order, the ticket, the item's own timeline.

Result: you see the event with its full history instead of a one-line summary.

What the system tells you

Some of these rows come with a letter as well. The rule is that a letter is sent when the news must reach somebody who is not looking at the screen; the letter and the row never replace each other.

The other direction also happens: several letters have no feed row at all — password changes, new sign-ins, invitations, two-factor changes, a voided certificate. Those are about your account, and an account event that only lived in a feed would be a security hole. The full catalogue is in Email templates.

Related

• Alerts — the queue behind every Fleet row, and the daily digest.
• Email templates — every letter Hafrix sends, and when.
• Roles & access — the two axes that decide which rows reach you.
• Basics — the capsule, the bell, toasts and dialogs.
• Admin settings — announcements, workspace settings, finance policies.

FAQ

A colleague got a row and I did not. Why? — Two filters run before a row is written: your role, and whether your group can see the section the row belongs to. Most system rows go to Manager and above; the connector row goes to admins only; the invoice rows go to anyone with the Invoices section, viewers included.

Why do I never get a row about the work I just did? — By design. Your own action is answered by the toast in the bottom-right corner. Rows exist for people who were not there.

Can I turn some of these off? — No. There is no notification preferences page, and no screen for the fleet mailing list either: the letters go to every manager and admin, or to a list of addresses set up for your workspace on request. Ask support if that list needs to change.

A row shows a code instead of a sentence. — That row's code is newer than your app's dictionary. Report it: the words exist, they just have not reached this build.

The badge is at zero but the tab counts still show numbers. — Mark all read clears unread; the tab counts on /notifications count live rows, read or not. A row leaves a tab only when its reason is gone.

How fast do notifications arrive? — Within a minute. The app asks the server every 60 seconds, and Time to reorder asks the warehouse for below-minimum stock every 30. Nothing is pushed instantly.

I acknowledged a fleet alert and it is still there. — Acknowledging says "seen, taken up"; it does not fix anything. The row closes when the finding stops being true — renew the certificate, top up the stock, log the maintenance.