Notifications

FMX can notify you when things you care about happen — a work request is assigned to you, a booking needs your approval, something you submitted is resolved. Notifications arrive as email, as browser push notifications, or in the in-app notification list, depending on your preferences and what your organization has enabled.

What can trigger a notification

Notifications are organized by category — your own records versus all records, per module. For example: My Work Requests vs All Work Requests, My Schedule Requests vs All Schedule Requests, and similar pairs for equipment, inventory, purchase orders, and invoices.

Within each category, you subscribe to specific events. Each option completes the sentence "Email me when a work request…" — for example:

• Is assigned to me
• Needs my approval
• Is overdue
• Is created by me

There are dozens of these events across the modules your organization uses, covering creation, updates, approvals and declines, due dates, and more.

Where your defaults come from

You don't start from a blank slate: your initial notification settings are the defaults defined on your user type. That's why a technician and a requester at the same organization get notified about different things from day one. From there, you can adjust your own preferences — see Managing Your Notification Preferences.

Notifications and the approval process

If your user type makes you an approver, "needs my approval" notifications are how requests reach you — you don't have to watch a queue. Approving or declining then notifies the requester in turn. See the request lifecycles in Work Requests and Schedule Requests for where approval fits.

What's covered here

Whether this matches what you see

You'll only see notification options for modules your organization uses and records you have permission to see. Organizations also control the defaults, so two people with different user types will see different starting points.