Notifications and Delivery
How remoteEaze sends, tracks, and presents user notifications.
Last updated
Notifications in remoteEaze are operational records. They are created, delivered, and tracked with the same control mindset used elsewhere in the platform.
Two notification paths
The platform currently supports:
- template-driven notifications triggered by system workflows
- admin-published announcements sent to a selected audience
Admin-published announcements are in-app notifications.
User experience
Users receive notifications through the in-app inbox, with support for:
- unread counts
- read and read-all actions
- dismiss/hide behavior
- real-time updates when connected
If a user reconnects, the inbox state is replayed from stored records.
Configuration and audience control
Notification policies can be configured per tenant, including:
- whether a policy is active
- channel selection within allowed policy rules
- audience block rules
Where policy changes are sensitive, workflow controls and approvals apply.
Delivery behavior
Notification dispatch can run asynchronously when fan-out is needed. This keeps user actions responsive while delivery is processed safely.
The system tracks delivery outcomes and avoids duplicate active records where dedupe rules apply.