🔒 New browser security hardening is live to help defend against AI-driven attacks. Learn more

eShare 155 Release Notes

Prev Next

This document describes the features, enhancements, and bug fixes included in eShare Release 155.

New Features

  • Navigation Button for Accessing Cloud Provider Storage and Native UI: From the Cloud Provider selection menu on the Cloud Provider page, a button is now adjacent to each item in the dropdown menu. This button, when clicked, will navigate the user to the selected cloud provider's native site (e.g., SharePoint, OneDrive) in a new browser tab. This allows the user to easily view, edit, and manage files within the native cloud file storage system.

Enhancements

  • Enabling Informational Notifications Across the Organization: In release 153 we stopped sending 4 types of informational notifications (Trusted Share Uploads, Trusted Share Access, Access Link in Use, and Compose/Reply in secure conversation except for mentioned users). At the request of some clients, we have made these notifications configurable as a group on a per-client basis. To enable these notifications for your organization, please contact your customer success manager. These notifications are not being sent by default.

Bug Fixes

  • The confirmation email sent to users when their Share With Me link was used by external parties to create a Trusted Share included a "Click to Deactivate this Share" button. But with some email security systems automatically opening all links in inbound emails, this would cause newly created shares to be unintentionally deactivated. To eliminate this possibility, the deactivation button has been removed from the notification email. Users can disable any unwanted shares within the share itself.

  • Inside a Shared With Me Trusted Share, the process to pin a file or folder would fail if the item had previously been flagged as a Favorite within the share. This issue has been corrected.

  • When a new user was logging into eShare using their company SSO login, a new user/identity was being created without the email address being set as "primary." This was a Power BI reporting issue and has now been corrected.