Thanks for the feedback and it is good to hear that the approach of going towards tags/hashtags makes sense.
I have some comments to the input from Laimonas
1 & 3etagging all documents is not really possible because that could lead to changing tags that other users have added. We could look into changing tags that you yourself has added, but not tags that others have added. The same goes for deletion.
4. Having tags as document metadata is something that SharePoint is looking into. Our goal as a platform is to move towards more shared gestures, but unfortunately I can't give you any details on the timeline for this other than that we are working on it.
Hi. I am a program manager working with boards in Delve. The underlying issue here is that a board i really a collection of documents that share the same tag. If you think of a board as "show me all items tagged 'LasVegasConference' that I have access to" then it follows that the way to make sure there are no documents on a board is to remove/rename the tag on each of the documents shown on a board. If you no longer want the board to show up for you, what you need to do is to remove it from your favorites. We recently consolidated favorite docs and favorite boards under the star in the left pane, so that is how you can get to all boards you've added docs to or favorited before.
Perhaps the ask that remains is that you do not want empty boards to show up in suggestions or in search results. This is something we're looking into. Remember though, that if a board looks empty to you, that may be because you happen to not have access to other documents tagged with that board name.
I would be grateful to hear back as to whether this model of thinking of boards as tags makes more sense to you and helps explain why they behave the way they do today.
This capability has already rolled out to activity pages in Delve, and we are working on adding it to other pages as well.
I am a Program Manager working on boards, and we are looking into how we tie this concept together with SharePoint so they do not exist in isolation in Delve. That's all I can share for now.
We’ve implemented the ability for end users to change the background image, chosen by a set of pre-defined images.
Thanks for the feedback! This was implemented with the focus of allowing users to personalize their profile background, not with a whole-company branding focus. Your feedback is great , though, and we'll take it into account when discussing next steps for this feature.
40 votes7 comments · Office 365 Security & Compliance » Message Encryption & Rights Management · Flag idea as inappropriate… · Admin →
Take a look at “decrypt rule” in this help topic:
Please let us know if this doesn’t meet your requirements.
Thank you for the feedback. It would be nice perhaps if the client could streamline the authentication (so we will leave this open).
However, the design to not decrypt mail that originates from another Office 365 tenant at the server level is intentional -- each sender controls exactly who can decrypt the message. If it was able to be decrypted at the receiving organization level, then a rogue administrator or someone else might be able to see the message contents. By forcing end user authentication, this problem is avoided and the sender controls exactly who may decrypt. The organizational decrypt rule works for conversations which that organization owns.