Mute the Email, Keep the Alert
An inbox full of reminders gets filtered, and then the reminder that mattered goes with the rest. Switching off the email should not mean switching off the alert. How to keep one and lose the other.
Every operations team reaches the same moment. The low-stock email arrives every morning, somebody builds an inbox rule to file it, and three weeks later a branch runs out of the item the email was about. The email was not the problem. Having only one way to hear about it was.
The short version
Treat email and the in-app notice as two separate switches on the same alert. Mute whichever channel your team ignores; keep whichever one they actually read. In AWRA OpsHub every email to your people now has an in-app twin, and the two switch independently.
One alert, many doors
An alert is a fact about your operation: an item is below its reorder level, three purchase orders are overdue, a leave request has waited past its approval time. A channel is just the door it comes through. Most systems weld the two together, so the only way to quiet the door is to brick up the fact behind it.
In Settings → Notification preferences each alert is one row, and each channel is a column: in-app, email, Slack, Microsoft Teams, WhatsApp, Telegram, Discord, Google Chat, SMS and push to the phone app. Switching one column off changes that door and nothing else.
| You want | In-app | What your team gets | |
|---|---|---|---|
| Both, the default | On | On | The email, and the same notice in the bell |
| A quieter inbox | Off | On | The notice in the bell only — nothing lands in anyone’s mail |
| People who live in email | On | Off | The email only; the bell stays clear of it |
| Nothing at all | Off | Off | The alert is not raised for this workspace |
Why the second row is the one that matters
Email off, in-app on is the setting that saves a stock-out. The inbox stops filling, and the notice still lands in the bell of every person the email would have gone to, under the same row, with the same link back to the record. The storekeeper who never opens email sees it the next time they open the app; the manager who filtered the email no longer has a rule silently eating it.
Muting a channel is a preference. Muting the alert is a decision. They should never be the same click.
The workspace decides the doors; each person tidies their own bell
The channel grid belongs to the workspace and is changed by people who can manage settings, because it decides what reaches suppliers, approvers and the whole team. Underneath it, each person can still choose which categories show in their own bell — stock alerts, approvals, security sign-ins and the rest — without changing what anybody else receives.
A handful of rows cannot be switched off at all: notices about your subscription, a scheduled workspace deletion, and replies from AWRA support. They show Always on, and they are spaced so that “mandatory” never means “daily” — a notice you cannot switch off should get quieter explains the schedule.
Finding the row
A grid of forty notifications is only useful if you can find the one you are looking for. Sections carry plain names — low stock lives under Inventory & stock alerts, not under the name of the screen that raises it — and a search box at the top filters to the row you type: “low stock”, “leave”, “QuickBooks”.
Going further than the grid
The grid covers every alert the product raises today. Organizations with particular routing needs ask us for these.
Per-person channel choices
Each person choosing email or bell for themselves, inside what the workspace allows.
Quiet hours
Non-urgent alerts held overnight and delivered at the start of the working day.
Branch-level routing
A low-stock alert for one branch going only to that branch’s team.
How it works: tell us who should hear what, and we return a written scope and cost.
Ask about routingFive minutes with your notification settings
Which alert emails have inbox rules filing them?
Look for
Low stock, approvals, digests.
Then
Switch their email off and leave in-app on.
Who on the team never opens email at work?
Look for
Storekeepers, drivers, field officers.
Then
Make sure their alerts have the bell switched on.
Which alerts does nobody act on in any channel?
Look for
Confirmations of things that worked.
Then
Switch the whole row off.
Which alert would cost money if it were missed?
Look for
Stock-outs, overdue deliveries, failed syncs.
Then
Keep two channels on for those.
What AWRA OpsHub does today
- One row per notification, one column per channel, set for the whole workspace
- Email and the in-app notice switched independently on every row
- An in-app copy of every email sent to your people, addressed to the same people
- Each person filtering their own bell by category
- Plain section names and a search box on the settings screen
More we can add to your workspace
- Per-person channel choices within the workspace’s settings
- Quiet hours that hold non-urgent alerts until morning
- Routing an alert to one branch’s team rather than the whole workspace
Where we point you to a specialist
- Notices about your subscription, a scheduled deletion and replies from AWRA support stay on — they are how we reach the people responsible for the account.
Keep the alert, lose the noise
Open Settings → Notification preferences and search for the alert your inbox has been filing.
Talk to us about your alertsFrequently asked questions
Can I stop AWRA OpsHub emails without missing the alerts?
Yes. Switch the email column off for that notification and leave the in-app column on. The same notice still reaches the same people in their notification bell, with a link to the record.
Who can change notification settings?
The channel settings belong to the workspace and are changed by people with permission to manage settings. Each person can still choose which categories appear in their own bell.
Which channels can a notification use?
In-app, email, Slack, Microsoft Teams, WhatsApp, Telegram, Discord, Google Chat, SMS and push to the phone app. Chat channels need their connector set up first.
Why can I not switch some notifications off?
Notices about your subscription, a scheduled workspace deletion and replies from AWRA support are always sent, because they reach the people responsible for the account. They are spaced out so they never arrive daily.
