Forum Discussion
Current default behaviour for saving sent items in delegate and shared mailboxes is wrong
In the absence of Microsoft changing any default behaviours, they need to change the Admin Center UI for user mailboxes so that they reflect what can be seen in the shared mailboxes UI, where they have a subsection called "Sent items" where tick boxes can be used to manage this behaviour and can show admins, at a glance, what the status is for this behaviour.
As I said, it already exists in the Admin Center all they need to do is extend their own logic!
However, in the absence of any arguments to support that the current default behaviour actually makes sense, beyond some unsubstantiated and vague comments about compliance, my point about the current behaviour being wrong stands.
VasilMichev, Thanks for the response, Vasil. I am aware that delegate shared mailboxes are based upon user mailboxes (don't forget resource delegate mailboxes too, though they are not relevant here).
I appreciate there would be privacy and compliance issues here, which is my precise point for raising the folly of the current default setting.
I was wondering if you could confirm to me any examples of a scenario where it would be compliant for legal or privacy purposes for someone to send an email as someone else and the delegator not have any record of the email in their "Sent Items"? Because this describes the current default, whereby delegates, with send as permissions, are able to send emails with no copy, by default, going into the delegator's Sent Items. By the current default "logic" to be legally and privacy compliant, you would have to change this default, to allow a copy of sent items to be placed into the delegator's Sent Items, as that is the ONLY way, currently, to allow the delegator to see any emails their delegate has sent, as them. This logic also applies to delegates with send on behalf of rights and equally fails to make sense as the DEFAULT behaviour.
I am happy to be proved wrong by any examples of how this default behaviour makes sense in the majority of use cases, for simple business communications or legal requirements.