Managing Your Notification Preferences
How to control which FMX events email you or send push notifications.
Your notification settings live on your user record — open your own account settings to edit them. (Administrators with user access can also adjust another person's preferences from that person's record.)
Email preferences
The Email Preferences section lists each notification category your organization uses (My Work Requests, All Schedule Requests, and so on). For each one, check or uncheck the specific events you want — each option completes a sentence like "Email me when a work request… is assigned to me / needs my approval / is overdue."
A few things to know:
- "My" vs "All" categories are separate. Subscribing to My Work Requests → is overdue only covers requests connected to you; All Work Requests → is overdue covers everything you can see. Choose deliberately, or the "All" categories can get noisy at a busy organization.
- Filters — subscriptions can be narrowed with filters so only certain records (for example, certain buildings) trigger notifications, rather than everything in the category.
- The kill switch — if you want silence, there's an option labeled Never send me emails! that turns all notification email off.
Push notifications
If your organization uses them, the Push Notification Preferences section works the same way but delivers to your browser as push notifications instead of email. Email and push are configured independently — you can get pushes for urgent events and email digests for the rest.
Recurring report emails
Separately from event notifications, the Reports section lets you have reports emailed to you on a recurring basis, so a summary lands in your inbox on a schedule instead of you pulling it from Reporting.
If notifications stop arriving
If FMX email to your address bounces or gets marked as spam, FMX stops sending to that address entirely. Unchecking and re-checking events won't fix that — an administrator has to re-enable email on your user record. See Logging In and Account Access.
A worked example
A maintenance supervisor wants to know immediately when anything in her two buildings goes overdue, but doesn't want email about routine updates. She subscribes to All Work Requests → is overdue with a filter limiting it to her buildings, turns on push notifications for needs my approval, and unchecks the per-update email events. Urgent items reach her phone's browser, overdue alerts hit her inbox, and the play-by-play noise stops.