Forum Discussion
Is there a "Sent" folder for an O365 Group Conversation?
I agree that access to the "sent" folder would be appreciated. If we were to replace shared mailboxes (with send as permissions) with O365 groups, we would of course need access to the sent folder (at least), since that message would be essentially lost for the sender without access to it.
Classic scenario would be the office@domainname.com mailbox.
Also access to Contacts would be very useful...
Anyway, one of the problems with the current implementation, I guess, is that in the Sent folder there are also all the messages sent to the Group itsef from the members, i.e. messages that are surfaced (in the Inbox) as conversations.
The "natural" way to implement conversations would have been, IMHO, connecting from the first moment Groups to Yammer (as will happen in the future - but only optionally). In such a way, a fully functional shared mailbox could have been connected to a Group. But this has not happened...
cfiessinger, another problem is that MS marketing insists in saying that to every Group is connected a shared mailbox, which is technically true, but not with regard to features. Hence users, reading the marketing blabla, expect to find a fully functional shared mailbox, which unfortunately is not the case...
Just my opinion, of course...
- In general, at least in our world, Distribution Lists are for Notification, Shared Mailboxes are for email-based collaboration.
Replacing a Distribution List with an O365 Group creates a bunch of extra features that are not needed outside of notification. However, we typically package, SharePoint, Yammer, a Shared Mailbox, and a few other tools together as a collaboration set, which IMO is what Groups offers to replace. Instead now we have to keep the Shared Mailbox and Conversations which can serve two separate purposes, but could technically serve the same, simplifying the experience for users.
I can list probably a ton of specific use cases with more time.Perhaps I have not been clear...
I totally agree with you that ALL the functionalities of the underlying shared mailbox should be exposed in a Group!
Only, I am afraid that this will not happen, because the main purpose of the underlying shared mailbox in the current implementation is to give support to the conversations "space" and this makes difficult (or even impossible) full usage of the shared mailbox.
- So now in europe we have lots of cases where people are using shared mailboxes for service desks. So when an email comes, the team leader use outlook categorization to categorize ewch incoming email. Each category mapped to one of the team members.
So in away or another they are assigning each incoming email to one member to handle that email.
Now we tried to move them to O365 groups because they want to share files and have SP team site.
The surprise was office groups conversations doesn't expose the ability to assign categories.
This is a stopping factor for us to adopt groups.
I guess groups should able to replace shared mailboxes more than it is meant to replace DLs.
