Notification Settings
Company-wide rules: which events fire, on which channels, to which roles, and how to keep noise down
Notification Settings is the company-level control panel for which events emit notifications, on which channels, and to which audiences. It complements each user's personal notification preferences: company settings decide what is technically possible; each user can then narrow down further from their profile.
Where to find this page
Settings โ Notifications. Only roles holding the notifications:settings permission can edit this page โ typically ADMIN by default. Other roles see a read-only view that helps them understand what their company is sending.
- Open the side menu โ Click Settings in the top navigation
- Pick Notifications โ Side menu inside Settings
- Browse by event โ Each row is one event โ toggles per channel, audience selector
Channels per event
Every event has three independent toggles โ in-app, email, push. You can mix and match: for example, fire in-app + push for workOrder.assigned (the assignee needs to know immediately) but email-only for inventory.lowStock (the warehouse manager will see it in the morning batch).
In-app
Always reliable; appears in the bell. Use as your default.
Routed through Postal (primary) with Brevo fallback; respects user language
Push
Mobile only; requires the user logged in on at least one device
Per-role audience selection
Each row carries an audience matrix split into two groups: people related to the item (Creator, Assignee) and your company's roles. The role pills show the actual roles defined in your company โ including custom roles โ so the list always matches Settings โ Roles. The matrix is additive โ selecting both MANAGER and Assignee means the assignee gets a copy even if they aren't a manager.
Roles
Pick any role from the company's current role list, including custom roles. Renaming a role keeps your notification settings in sync automatically.
Assignee
Whoever the entity is assigned to (work order, request)
Creator
The user who created the entity
Team
Members of any team attached to the entity, including team leader
Quiet hours and digests
FreeMaint does not currently support a global quiet-hours window per tenant. Push notifications respect each user's device-level Do Not Disturb. For schedule-sensitive teams, pair the per-event row with the digest variant (e.g. workOrder.overdue โ workOrder.overdue.summary) so the firehose becomes a single morning brief.
Digest events
Some events have a companion daily digest row. The digest fires once per day at 7am UTC and aggregates everything that happened over the last 24 hours into a single message. Common digests: overdue work orders, low-stock summary, expired/expiring documents (Fleet). Turn off the per-event row and turn on the digest row to dramatically reduce inbox volume.
Email delivery setup
Outbound emails are sent from noreply@freemaint.com by default. Enterprise tenants can configure a custom from-address tied to their domain โ the setup requires adding SPF, DKIM, and a return-path DNS record. Contact support for the DNS template specific to your domain.
Best practices
Start narrow
Subscribe only assignees + creators by default. Expand to roles only once teams ask for it.
One channel per event
Sending the same event on three channels at once feels noisy. Pick the most appropriate (push for urgency, email for digests, in-app for everything else).
Audit quarterly
Review which events fire most often and ask whether they still need to. Mute or downgrade frequent low-value events.
Prefer roles over named users
Subscribing by role survives staff turnover; subscribing by name breaks when someone leaves.
Tip
Related articles
Was this page helpful?