Skip to content

Commit 47c6057

Browse files
Update Closeconversation.md
1 parent db0e545 commit 47c6057

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/en/Viva/Closeconversation.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ menubar: docs_menu
55
hero_image: '/img/IMG_20220521_140146.jpg'
66
show_sidebar: false
77
hero_height: is-small
8-
date: '2024-05-22'
8+
date: '2024-05-26'
99
---
1010

1111

@@ -47,9 +47,9 @@ There is a variety of reasons why you should be closing Viva Engage conversation
4747

4848
<img src="/articles/images/VivaCloseConversation4.PNG">
4949

50-
<h1>Step 3: How to reopen Viva conversations?</h1> <a name="closeVivaconversations"></a>
50+
<h1>Step 3: How to reopen Viva conversations?</h1> <a name="howtoreopen"></a>
5151

52-
<h1>Step 4: Who can? Required Permissions</h1> <a name="closeVivaconversations"></a>
52+
<h1>Step 4: Who can? Required Permissions</h1> <a name="permissions"></a>
5353

5454
Conversations that no longer
5555
Before the rollout, only a post creator can close conversations in Storyline and only the Community admins can close conversations on behalf of members in Communities. We are expanding the ability for delegates, delegate managers, Global admins, and Engage Admins to moderate Viva Engage content.

0 commit comments

Comments
 (0)