CrisisGo Integration and Captures updates (April 2026)
Release Date: 9 April 2026
Note
This Release Notes is for users of Monitor v2.0. For help accessing the new Monitor version, please contact your school’s Success Manager or our Support Team.
- Added a new CrisisGo integration with Alerting Profiles for customers in the United States.
- Improved the Captures modal by combining capture and device details in one screen. Captures now also support full-screen and mobile-friendly views.
- Improved navigation for the custom Alerting Profile creation page using your keyboard. Use Tab to move across elements, Arrow keys to expand lists, and Enter or Space bar to select items or confirm settings.
- Fixed the on-screen validation message for adding Safeguarding Contacts to Alerting Profiles.
- Fixed an issue that duplicated new custom Alerting Profiles for some users.
- Fixed an issue where signed-out users selecting an Alert link in an email notification were redirected to the Alerts dashboard instead of the specific Alert details page.
- Deactivated the Next Alert navigation button to indicate the Contact is viewing the last Alert.
- Fixed an issue with the Captures navigation using the left and right arrow keys.
Monitor for ChromeOS Extension 4.2.11 (March 2026)
Release date: 18 March 2026
- IT Admins can prevent the Monitor ChromeOS extension from running on unmanaged devices, such as users’ personal or home devices, or those that the school has exempted from monitoring.
- This update requires configuration from the Google Admin Console.
- IT Contacts can download the latest Monitor ChromeOS extension installer from Monitor.
Windows Client Update 2.10.2 (March 2026)
Release date: 6 March 2026
We’ve released the new Monitor Windows Client version 2.10.2.
- Improved detection of the Window title: Confidential systems are filtered, capturing only essential systems information.
- Faster screenshot generation: Reduced delay between trigger actions and screenshots, ensuring screenshots are taken before users switch tabs.
- Accurate reporting: Fixed a bug that caused Monitor to report Windows 11 devices as Windows 10.
Automoderation for low-level Sexual Content and Offensive User events (February 2026)
Release date: February 19 2026
- Sexual Content level 2 and Offensive User levels of 1 and 2 events are now sent directly to Safeguarding and Limited Safeguarding Contacts without human moderation. This change allows our Moderation team to focus on Events with high-level risks.
- These auto-moderated Sexual Content and Offensive User events are sent directly to the Monitor dashboard without screenshots and moderator comments.
- Monitor’s highly trained human moderation team will still review high-risk categories and severe alerts to ensure schools are contacted directly.
Older Release Notes (2025)
New Monitor client installers (November 2025)
Release date: 5 November 2025
New Client for Windows ARM Devices
- We have released a new dedicated client for Windows ARM devices.
- Download sw-safeguarding-client-arm64-2.10.1.msi from Monitor’s Client page or software.smoothwall.com
- See Install Monitor on Windows ARM devices for the installation and configuration instructions
Client Name Update for Windows x64 Devices
- Our existing Windows client has been updated with a specific architecture identifier.
- Download sw-safeguarding-client-x64-2.10.1.msi from Monitor’s Client page or software.smoothwall.com
- This client continues to support all x64-based Windows devices.
Users on ARM-based Windows devices must now use the new arm64 client installer and x64-based Windows devices should have the newly renamed x64 client installer.
Smoothwall Appliance Maiden-27 (March 2025)
Release date: March 11 2025
We’ve added users’ display names to the Events and Cloud Scan Media pages for directories that sync with the On-Premise Appliance.
Older Release Notes (2024)
Cloud Scan (December 2024)
Release date: 5 December 2024
- We increased the reliability of restoring file permissions when files are marked as Safe or Deleted.
- We improved Monitor's responsiveness when actioning flagged images.
- We stopped processing large Photoshop files that are incompatible with our image analysis library.
- We capped the maximum image size for processing to 100MB to reduce scan time and resource consumption.