Share, move, mute conversations in Engage

Move conversations

• You can move any and all conversations in public and private communities. Any user with access to a conversation can move it.

• In the community settings, admins can prevent users from moving conversations into their community. Admins can move conversations anywhere in Engage, regardless of this setting. Restricted communities don't allow users to move conversations in or out.

• All conversation participants before the move and all users with access to the new community can see the conversation after it's moved.

• Files remain in the original community, but links to the files still appear in the conversation in the new community.

• Everyone has access to files in conversations that move between public communities. If a conversation moves from a private community, only members of the community where the conversation was originally posted have access to its files. If the conversation gets moved back, anyone currently participating in the conversation (regardless of community membership) and all the original private community's members keep their access.

• You can only move from one community to another community. The post is only in the community where it's moved. It's not copied into both.

• You can move conversations multiple times.

• You can move conversations to any community they have access to (public or private), provided the admin hasn't restricted the moving of conversations.

• Users involved in the conversation get an inbox notification when a conversation is moved. A system message is added to the conversation when it is moved. The message includes who moved the thread, where it was moved from, and where it was moved to.

Share conversations

• You can share a conversation with anyone in your Viva Engage tenant. There is no limit to how many times you share a conversation. However, you cannot share conversations outside the tenant.

• You can't share a private message, but you can add more tenant members to your private message.

• When you share a conversation with a community, the shared message appears in the other community's feed, with a link back to the original conversation. Although community members where you're sharing it can see that message, the message also provides a link back to the conversation.

• A share functions like a forwarded email message because it creates its own, new version of the message. When you share a conversation, the message that you share becomes a conversation starter in its new community. The only connection to the original message is a link back to the original conversation.

• Messages from private communities can be shared, but only members of the private community can view the full conversation. Nonmembers see only the shared message.

• View Shares shows a list of all locations to which a message is shared. This is indicated by an icon next to the message. You can see only the names of the communities to which you belong or that are public and listed under shared conversations.

• To share a conversation with someone who isn't located on Viva Engage, share the conversation through private message, and then type the email address. That person will receive a Viva invite email message that states you shared a message with them.

Mute conversations (Engage admins and corporate communicators)

• After it's muted, the conversation doesn't appear in the home feed or the email digests of all network users. Users can still see the thread in communities, storylines, and through search.

• Muted conversations have a visible indicator for network admins and corporate communicators. No other users can see when a conversation is muted. Users aren't notified when a thread is muted.

• Muting conversations is independent from muting communities and muting users.

• You can check all activity from use of conversation muting through the Microsoft 365 user audit logs, including the following fields:

  • User ID of the user who muted or unmuted the conversation

  • Thread ID of the muted conversation

  • Date and time the thread was muted or unmuted Learn more