Guides
Notifications
Learn which events send a notification, who receives it, and at what level.
Miridia sends a notification when there is a reason to act or a fact that you need to know. It does not send a notification for each record that a person creates. The person who made the record already knows about it.
Where notifications appear
Each notification appears in two places:
- The notification bell in the portal. You can mark one notification as read, or mark all as read.
- A push message, if you enabled push messages in your browser.
A notification about a record has a link to that record in the portal.
Levels
| Level | Use |
|---|---|
Info | A fact that you need to know. |
Success | A process finished correctly. |
Warning | Something needs your attention. |
Who receives a notification
- Business: each employee of the business.
- Role: each employee with a specific role, for example
AdministratororManager. - One user: one named person, for example the assignee of a work order.
The notification list
Orders
| Event | Receives | Level | Message |
|---|---|---|---|
| A new order arrives from a sales channel | Business | Info | New order '{code}' from {channel} |
| An order is complete | Business | Info | Order '{code}' is Complete |
| An order is cancelled | Business | Warning | Order '{code}' is Cancelled |
An order that a person enters in the portal sends no notification. Other status changes send no notification.
Shipments
| Event | Receives | Level | Message |
|---|---|---|---|
| A shipment is delivered | Business | Success | Shipment '{code}' delivered |
| A shipment is cancelled | Business | Warning | Shipment '{code}' cancelled |
| A carrier quotation is accepted | Business | Info | {carrier} booked for '{code}' at {price} |
| A collection is requested | Business | Info | Collection requested from {carrier} for '{code}' |
Inventory, purchasing, and transfers
| Event | Receives | Level | Message |
|---|---|---|---|
| Stock goes below its reorder point | Business, role Manager | Warning | {sku} at {location} is under its reorder point ({balance} of {reorderPoint}) |
| A purchase order is received | Business | Success | Purchase order '{code}' received |
| A transfer order is received | Business | Info | Transfer '{code}' received |
| A transfer order is rejected | Business | Warning | Transfer '{code}' rejected |
Production
| Event | Receives | Level | Message |
|---|---|---|---|
| A work order is complete | Business | Success | Work order '{reference}' completed, {qty} {sku} produced |
| A work order is cancelled | Business | Warning | Work order '{reference}' cancelled |
| A work order is assigned to a person | That person | Info | Work order '{reference}' has been assigned to you |
A work order with no assignee sends no notification when you create it.
Team and integrations
| Event | Receives | Level | Message |
|---|---|---|---|
| A new user joins | Business, role Administrator | Info | {name} joined the business |
| An integration is activated | Business, role Administrator | Info | The '{provider}' integration has been activated successfully |
| An integration is deactivated | Business, role Administrator | Info | The '{provider}' integration has been deactivated |
Other notifications
- Miridia AI Studio raises its own findings in the findings inbox. Read Miridia AI Studio.
- Miridia Planner shows its exceptions on its notifications page. Read Miridia Planner.
Send a notification to another channel
To send an event to email, Slack, Telegram, or another channel, build a workflow. Each event above also has a workflow trigger. Read Workflows.
For an important workflow, add an error path in your workflow engine. Then a failed step alerts a person.