Skip to main content

End-User Notifications Overview

Now, admins using FileWave Anywhere, FileWave Central, or API calls can send custom messages to enrolled devices, displaying them as system notifications for users. This feature empowers administrators to communicate important information directly to users' devices, enhancing engagement and user experience.

Key Functionality:

  • User-Friendly Interface: Administrators can easily send notifications by selecting one or multiple devices or groups and accessing the "Send Notification" action.

  • Customizable Content: Administrators can personalize notifications with titles, authors, text content, and optional links.

  • Expiration Date: Notifications can be set with an expiration date to ensure timely delivery and relevance.

  • Platform Compatibility: Notifications are supported across macOS, Windows, iOS, iPadOS, ChromeOS, and Android devices.

  • Client Compatibility: Notifications are supported for clients that are on version 15.5+

  • History: Sent Notifications are available in Audit History.

  • Validation and Error Handling: The system ensures mandatory fields are filled and provides clear error messages for invalid or unsupported devices.

User Experience:

  • Confirmation Dialog: Users receive a confirmation dialog after sending notifications, providing assurance and transparency about the sent notification.

When device will not receive a notification?

iOS/iPadOS

  • Client is < 15.5.0 version.

  • FCM didn’t register the device (the user hadn’t opened the App portal ever since enrollment).

macOS

  • CliClient is < 15.5.0 version.

  • Kiosk running any issue.

Windows

  • Client is < 15.5.0 version.

  • Kiosk running any issue.

Chrome

  • FCM running issues.

  • Chrome extension is pinned to earlier version(s).

  • If one user has read a message, other users can’t see the notification due to technical limitations.

Android

  • FCM didn’t register the device.

  • FW Client running any issue.

Behavioral specifics

General (all platforms)

  • When sending notifications with a specific expiration time, the expiration will occur at the exact time specified, regardless of the recipient's time zone. For example, if a notification is set to expire at 2:20 PM UTC, it will expire at 2:20 PM UTC for all recipients, no matter their local time. Therefore, a user in the United States (Eastern Daylight Time, EDT), where the current local time is 7:20 AM, will see the notification expire at 7:20 AM EDT. This ensures consistent behavior across all time zones.

iOS/iPadOS

  • The expiration date is checked on the Apple side - the notification may be still valid when checked on Apple servers - but not valid for the device → In this case - the notification will be visible, but when clicking on the notification only App Portal without full notification will be displayed.

  • Notifications are only delivered to the user who is currently logged in on the iPad.

  • Logged-out users do not receive any notifications sent while they were logged out, regardless of how many were sent.

  • If a user is logged in and receives notifications, those notifications are not delivered to other users who log in afterward.

macOS

  • If multiple users use the same device, each user will receive a notification.

  • If the notification is not read, but still valid, and the Notification Center gets cleared (or the device gets restarted) - after a new notification arrives, all old unread notifications that are valid are going to be listed in the Notification Center again.

  • After the expiration date/time is reached, a cleanup period needs to happen in macOS (1 hour by default) before the notification disappears from the Notification Center.

  • If the Kiosk is not visible by default, it will temporarily appear when Notification details are displayed and will be removed from the UI once the Notification is closed.

  • There is a possibility of automatically enabling notifications using Notifications Apple Profile (this will disable user of turning of Notifications for the Kiosk app): LINK

Windows

  • If multiple users use the same device, each user will receive a notification.

  • If the notification is not read, but still valid, and the Notification Center gets cleared (or the device gets restarted) - after a new notification arrives, all old unread notifications that are valid are going to be listed in the Notification Center again.

  • If the Kiosk is not visible by default, it will temporarily appear when Notification details are displayed and will be removed from the UI once the Notification is closed.

Chrome

  • If one user has read a message, other users can’t see the notification due to technical limitations.

Android

  • Expired notifications are not removed from the preview and can still be opened.

  • If an Android device is turned off and a notification expires during that time, the device will not receive the notification when powered on.

 

Back to top