AWRA OpsHub Search

AWRA Help Center

Copy link
Help Workflow Support
01 Notification Problems Troubleshooting 02 Connectors Directory Integrations

Notification Preferences

Choose which notifications your organization receives and on which channels — in-app, email, push, SMS, Slack, Teams, WhatsApp, Telegram, Discord or Google Chat — and how often reminders repeat.

Notification preferences live at Settings → Notification Preferences. The screen is a grid: one row per notification, one column per channel. Tick where a notification should be delivered, and leave the rest clear. Everything is saved through one path, so what the grid shows is what will actually be sent.

The Channels

In-app, Email, Push, SMS, Slack, Microsoft Teams, WhatsApp, Telegram, Discord and Google Chat. Most are on by default; SMS and WhatsApp are off by default because they usually cost money per message. A chat or messaging channel only delivers once the matching connector is configured — see Connectors Directory. Ticking a channel with no connector behind it changes nothing on its own.

Reminder Cadence

Some rows are reminders rather than one-off events — an approval still waiting, stock still low, a plan about to expire. Those rows carry a cadence control: how often the reminder repeats, and at what interval in days. This is the setting to reach for when a digest feels too noisy or too quiet; turning the notification off entirely is rarely what you actually wanted.

Assets Rows

The Assets section carries two daily reminders: Asset Returns Due or Overdue (admins get the full list, each custodian their own items) and Asset Warranties Expiring (admins). Each has its own email and in-app switch; how far ahead they start is set in asset settings. See Asset Reminders. The section also holds pooled-asset movement approvals and risk events.

Date Reminders

A set of reminders is driven by the dates on your records, checked each morning at 07:40 East Africa Time, and each has its own row: Supplier Bills Due Soon or Overdue and Last Month Not Closed (Accounting), Stock Count Due or Overdue and Stock Hold About to Expire (Adjustments), Customer Quote About to Expire and Sales Order Past Its Expected Date (Customer Invoices), Leave Starting / Ending, Expense Claim Left in Draft, Last Month’s Timesheets Not Approved and the two clock-in and clock-out reminders (HR), and Access Review Due or Overdue (Security). Their timing is built in, so these rows carry no cadence control: each goes once per stage (as the date approaches, and once if it passes), and team backlogs repeat weekly. Untick email, in-app or push on a row to stop that channel, or all three to stop the reminder. Employees are only ever reminded about today, never about a past day. The details are in Supplier Bills, Month-End Close, Inventory Counts, Stock Reservations, Quotes & Sales Orders, Leave, Expense Claims and Attendance & Time.

You Only See What You Have

The grid shows the notification modules relevant to your organization and your access. A module you do not use does not clutter the list. So two administrators can legitimately see different rows.

Organization Settings, Not Personal Ones

This screen is an organization-level configuration: viewing it needs the settings view permission and saving needs settings management. Your own personal details and reminder settings are under Profile Setup, and how notifications are displayed to you is under Notifications → Display Settings.

Push Notifications

Push delivery has its own page under Settings → Push Notifications, where you can send a test to a device, check delivery health, retry failed sends, and clear out stale device registrations. A push that never arrives is usually a stale registration rather than a preference — start there, then see Notification Problems.

If Email Is Missing

Check the email column is ticked for that notification, then check Email Logs to see whether the message was sent at all. A message that was sent and not received is a mailbox or spam problem; a message that was never sent is a preference or a data problem.

Need help with this topic?

Capture the module, record number, branch or warehouse, user, visible message, and what you expected to happen before contacting support.

Open support guide