eShare 140 Release Notes
NEW FEATURES
-
Convert native Microsoft file/folder links to eShare links within Secure Conversations
In Release 137, we introduced the ability to convert native Microsoft file/folder links to eShare links when Trusted Shares are created via the Secure Mail Gateway. We have expanded our support for native Microsoft links to include their inclusion within Secure Conversations. More specifically, when users paste native Microsoft file/folder links into Secure Conversations the linked file/folder is incorporated into the Trusted Share at its root. Linked items have a special icon but are otherwise indistinguishable from other files/folders within the share.
Note that the linked file/folder is not copied into the Trusted Share. The share contains a link to the file/folder, with the file/folder stored in its original location (e.g., SharePoint document library) from which the native Microsoft link was generated.
Enabling this link conversion is achieved when the policy option “Convert native Microsoft file/folder links in email body to Trusted Share links” and “Use sharing policy for Secure Mail Gateway” is enabled within the sharing policy that is applied to the Trusted Share. This requirement will be changed in a future release, with link conversion occurring independent of the Secure Mail Gateway (i.e., Secure Mail Gateway is not required).
-
Inherited label for native Microsoft file/folder links that are not explicitly labeled
When an unlabeled file or any folder within SharePoint is incorporated into a Trusted Share via a native Microsoft link, we now look for that SharePoint site’s label. If a SharePoint label exists, we factor that label into our sharing policy decision making when actions are performed on the linked file/folder within the Trusted Share. (e.g., file open, folder download).
This inherited label allows the linked file/folder’s SharePoint site label to be used in determining the applicable sharing policy, in the same manner as would occur were the linked file/folder to be shared from that SharePoint site directly using eShare (i.e., not via a native Microsoft link). There is no admin configuration or sharing policy option required to utilize this feature.
-
Pinning Trusted Shares in the Shared With Me page
In Release 139 we added the ability to pin Trusted Shares to the top of the My Shares page. We have expanded this ability to also include the Trusted Shares within the Shared With Me page.
ENHANCEMENTS
-
Configurable header
The brand/logo header used at the top of email notifications sent to recipients of Trusted Shares created by the Secure Mail Gateway is now optional. This allows Trusted Share emails created by the Secure Mail Gateway to more closely resemble the look and feel of the sent email were it and its attachments not protected by eShare. This selection is made within the “SMG email branding” page of the Admin Console.
-
Shareable link enhancement
We have updated our “Copy Shareable link” feature to provide an improved workflow when it is used by users who are not existing recipients of a Trusted Share. This results in a Shareable Link behaving like an Access Link. Upon accessing a Shareable Link, the unknown user will be required to input their email address, to which a recipient-specific link will be emailed. If the Trusted Share owner’s approval is required per the sharing policy of the Trusted Share, this approval will be sought of the owner prior to a link being sent to the recipient.
-
Secure Mail Gateway Trusted Shares
Up until this release, Trusted Shares created by eShare’s Secure Mail Gateway did not support the “Make all internal recipients as co-owners” setting of a sharing policy. With this release, internal recipients of an email that is processed by Secure Mail Gateway will be added to the created Trusted Share as co-owners.
-
Support for dark mode email templates
eShare secure email notification templates now support dark mode when viewed within Microsoft Outlook and Apple Mail.
-
Display Name of users
We now show the “Display Name” of a user in our email notifications, if it has been made known to us via SSO from Microsoft Active Directory. Prior to this release we always showed the full name of the user as it was input into eShare at the time of the user’s initial eShare registration.
BUG FIXES
-
There was an issue in the “Secure mail” section of the Admin Console, that would allow multiple entries of the same email address to be added in the BCC recipients field. This has been corrected and only one entry of the same email address should be present on the list.
-
There was an issue when enabling the Share With Me link feature on a SharePoint site that would cause the link to not be available until the administrator refreshed the page. This has been corrected and the link should be immediately available.
-
There was an issue that would prevent copy/move actions of a file from a folder to the root section of a Trusted Share, even though the Task Manager displayed the action as completed. This has been corrected and should no longer be the case.
-
There was an issue with internal recipients being unable to access a Trusted Share created via Access Link when a certain combination of options was enabled. This has been corrected and should no longer be the case.