eShare 152 Release Notes
NEW FEATURES
- Trusted Shares can be created with only Upload being allowed
Prior to this change a Trusted Share required that View and/or Download be enabled. This requirement has been removed, allowing shares to be created with only Upload being enabled. This provides share creators with more control over recipient rights within Trusted Shares.
ENHANCEMENTS
- File access request with justification & override now supports DLP Tags
When a file’s DLP Tag prevents a recipient from viewing, editing or downloading the file based on the sharing policy applied to a Trusted Share, the sharing policy can be optionally configured to allow the recipient to request access, with both the recipient and share owner being required to input a business justification to override the blocking action. Previously, this override was only allowed when a sensitivity label was the basis for the blocking action.
BUG FIXES
- When multilingual Sensitivity Labels are configured within M365, we were not retrieving the English names for display within the Cloud Web Portal. This has been corrected and should no longer be the case.
- The Last Access field on the Shared With Me page did not update for co-owners when external users accessed a Trusted Share. This issue has been fixed and should no longer occur.
- When a Trusted Share co-owner used the Get Shareable Link function, distributed the link to a recipient, and the recipient accessed it, the owner of the Trusted Share had to approve the invitation. With a Trusted Share co-owner having the same rights as the owner in inviting recipients to access a share via Get Shareable Link, this approval should not be required. This issue has been fixed and should no longer occur.
- When <consumer domains> list is used in sharing policies to define allow/block lists, the evaluation of that list allowed for partial matches. The domain part of recipient email addresses (after the @ sign) is now evaluated on an exact match basis.
- The option “Allow recipient to request access to shares & files that this policy’s sensitivity label or tag would otherwise block” was hidden on policy setup. This issue has been fixed and should no longer occur.