Notifications
Notifications are how OnlyTons nudges the right person at the right moment — above all, how the broker learns that a demand needs matching.
Where they appear
The Notifications item in the sidebar shows an unread badge. Open it for the full list; opening a notification takes you to the thing it's about (a demand's matching workspace, a deal, and so on).
Types of notification
| Notification | Goes to | Meaning |
|---|---|---|
| Demand needs matching | Broker | A buyer posted a demand — start matching |
| Deal status changed | Deal parties | A deal you're part of moved stage |
| New message on a deal | Deal parties | Someone posted a shared message |
| Certification expiring | Broker | A certification is ~30 days from expiry |
| Commodity requested | Broker | An org asked for a new catalog product |
| Organization verified | The org's users | The broker verified your organization |
| Reliability band changed | The org's users | Your reliability band moved down. A band that moves up is deliberately silent — you do not need warning that things are fine |
| Review closed | The org's users | The review you asked for has been decided |
| Reliability review needed | Broker | Something needs a person: a proposed block, contradictory information, an operator contesting a decision, or a periodic audit |
Notifications respect deal visibility — you're only notified about deals you're a party to, and never about internal broker activity.
The broker's most important one
"Demand needs matching" is the heartbeat of the workflow. When a buyer publishes a demand, the broker gets this notification; clicking it opens the matching workspace for that demand. In the 90-second demo, this is step one.
Under the hood: notification text is assembled from message templates in the app's message catalog, so it's translated along with the rest of the interface — the stored notification carries a type and data, not a hardcoded English string. See Languages & localization.
Next: Languages & localization · Back to index