In-App Notifications
The bell icon in FMX — what shows up there, who gets notified, and how it differs from email and push.
Alongside email and push notifications, FMX keeps a notification list inside the app itself. The bell icon in the header shows a count of your unread notifications; selecting it opens a Notifications panel with your five most recent. View all opens the full notifications page, and Mark all as read clears the unread count. Clicking any notification takes you to the record it's about.
What shows up there
In-app notifications cover activity on work requests, work tasks, schedule requests, transportation requests, purchase orders, invoices, equipment, and inventory items — creation, responses, assignment, approvals, and similar events, for the modules your organization uses.
Unlike email and push, you don't pick which events appear here. In-app notifications go to the people connected to the record: whoever it's assigned to, whoever requested it (or had it submitted on their behalf), and anyone following it. You won't get in-app notifications for your own actions — FMX skips notifying you about changes you just made.
Mentions
If someone mentions you by name in a work request response, you get a notification that they mentioned you — a good reason to check the bell even if the request isn't yours. Mentions still respect visibility: you won't be notified about a private response you couldn't read.
How it differs from email and push
| Channel | You control it via | Where it arrives |
|---|---|---|
| Email Preferences | Your inbox | |
| Push | Push Notification Preferences | Browser/device notifications |
| In-app | Not configurable — based on your connection to the record | The bell icon |
Turning off emails ("Never send me emails!") doesn't touch the in-app list, and subscribing to more email events doesn't add in-app notifications — the two channels are decided independently.
Housekeeping
Notifications are kept for about a month, then removed automatically. There's no way to delete individual notifications — mark them read and let them age out. The unread count refreshes as you move between pages, so a notification triggered while you sit on one screen appears the next time you navigate.
A worked example
A technician resolves a plumbing request and mentions the front-office manager in the resolution response. The manager — who has work request emails turned off — still sees a badge on the bell the next time she loads a page. The notification says the technician mentioned her; clicking it opens the request, where she reads the resolution note and closes the loop without a single email.