Configure and manage notification preferences and alerts
How FreeMaint keeps you informed
Three channels: in-app, email, and mobile push.
Colour tells you the state; the icon and the label tell you the subject. A category label sits under every notification, so the colour is never the only cue.
Configure preferences early to avoid notification fatigue.
What triggers a FreeMaint notification, which channels carry each event, and how to tune who hears what
FreeMaint emits notifications when work orders, intervention requests, preventive maintenance plans, parts inventory and other entities change state. Every event flows through three delivery channels (in-app, email, push) and can be tuned per role, per channel, and per quiet-hours window.
Every notification can be delivered through three independent channels. A single event can fire on one, two, or all three — administrators control the matrix per event per role from the notification settings page.
Some events have both a per-occurrence channel and a daily roll-up digest. The classic example is overdue work orders: enabling workOrder.overdue floods recipients one email per WO, while workOrder.overdue.summary sends a single morning brief with the full list. Choose whichever matches your team's tolerance for inbox noise. Each recipient only finds the items their role's data visibility shows.
Each event corresponds to a specific state change in the system. Events are emitted at the source of the change — for example, when a work order is assigned, when a request is closed, or when stock drops below the reorder point — and are then routed to the recipients configured for that event.
Push and in-app channels respect the recipient's profile. Email subjects and bodies are translated into the user's preferred language at send time, regardless of the actor's language. There is no global quiet-hours window today — schedule-sensitive events should be opted out per recipient via the personal preferences page.
Recipients are resolved at emit time based on the event configuration. The same event can target different audiences depending on the role mapping you choose.
Turn these on to be told when someone enters an asset or a location by hand — useful while several people are building out the system. Bulk imports and asset duplication never trigger them, and a daily ceiling per person keeps a busy day from flooding your inbox. Both are off by default.
Subscribe by role rather than by named user. When you onboard a new manager, they automatically inherit the matrix; you don't have to remember to wire them in.
Issue: A user is not receiving an event they should
Solution: Check the event row in Settings → Notifications: is the relevant channel enabled, and does the role list include this user's role? Then check the user's personal preferences.
Issue: Emails arrive but pushes don't
Solution: The user must be logged into the mobile app on at least one device. Re-login if they recently changed phone.
Issue: Same event arrives twice
Solution: User probably has two roles that both subscribe (e.g. ADMIN + MANAGER on the same row). Dedup is per-channel, not cross-role — adjust the row to a single role.
Issue: A user is not receiving an event they should
Solution: Check the event row in Settings → Notifications: is the relevant channel enabled, and does the role list include this user's role? Then check the user's personal preferences.
Issue: Emails arrive but pushes don't
Solution: The user must be logged into the mobile app on at least one device. Re-login if they recently changed phone.
Issue: Same event arrives twice
Solution: User probably has two roles that both subscribe (e.g. ADMIN + MANAGER on the same row). Dedup is per-channel, not cross-role — adjust the row to a single role.
Customize your notifications
Control which events trigger alerts and through which channels.
Digest alerts (low stock, overdue work orders, overdue PMs, expiring contracts…) repeat only while the situation is unresolved. You are notified once when it appears, again whenever it changes, and then at the cadence you choose. Set it per event under Settings > Notifications: Only when it changes, or every 1, 3, 7, 14 or 30 days. Default: every 7 days.
Keep: WO assignments, request approvals, critical stock alerts.
Email setup
Sent via Brevo SMTP with direct links to FreeMaint.
Free plan: 300 emails/day. For high volume, upgrade Brevo or use in-app/push.
Add contact@freemaint.com to safe senders.
Mobile alerts
Real-time alerts on your phone.
Enable only work-relevant notifications.
FreeMaint CMMS
© 2026 FreeMaint. All rights reserved.