2023.9 Service Update
December 14, 2023
Release Notes
We're happy to bring you our 2023.9 Service Update. The stability of our service is always central to our development efforts. All service updates contain improvements related to that goal in addition to the updates listed below.
Features
With this release, we're pleased to deliver self-provisioning for new File Protection Manager users via KaseyaOne, the customer portal and central hub for all modules that belong to the Kaseya IT Complete portfolio. This feature is part of our KaseyaOne Unified Login initiative, which will provide you with centralized user management and access control.
For detailed information about how to enable automatic user creation, please refer to Enable automatic user creation. For general information about our KaseyaOne integration, including how to enable it, refer to KaseyaOne Unified Login. For information about accessing modules like File Protection from KaseyaOne, please refer to this article in the KaseyaOne online help.
In a related change, we've added the ability to disable login via KaseyaOne.
Enhancements & changes
In the interest of greater clarity regarding security and feature access, we've changed the names of the permissions levels available to File Protection Manager users. Manager Administrator is now Full Access. Team Administrator is now Team Access. And we've simply removed the hyphen from Read-Only, making it Read Only. There are no functional changes; this is solely a labeling change.
For more information about permissions and security, please refer to About security levels and permissions.
Fixes
In addition to the issue resolution listed below, we continue to make minor adjustments to the interface and implement general enhancements to improve security, stability, performance, and your overall end-user experience.
Required events did not take place when a backup restore executed by an administrator failed. The team administrators, any File Protection Manager users who are notification recipients, and potentially the device owner (depending on specific configuration) should have been alerted via email notification. If automated ticketing integrations are configured, the event should also trigger the creation of a ticket in the associated app. These issues have been resolved and all required events are now executed.