Skip to content

Commit ca51f67

Browse files
000-508: removeresources
1 parent 7f84473 commit ca51f67

File tree

1 file changed

+34
-8
lines changed

1 file changed

+34
-8
lines changed

articles/en/Viva/removeresources.md

Lines changed: 34 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -47,25 +47,51 @@ When a community is created in Viva Engage, the system generates a SharePoint si
4747
### Document Libraries
4848

4949
**Purpose**: To organize files and media shared in the Viva Engage community.
50+
5051
**Mechanism**: Libraries for documents, images, and other files are created within the associated SharePoint site.
52+
5153
**Why**: Organizing media helps ensure content is easily searchable, accessible, and manageable, especially when communities grow in scale and file-sharing increases.
5254

5355
### Microsoft 365 Group Creation
56+
5457
**Purpose**: The community is also supported by a Microsoft 365 group that grants permissions, handles membership, and offers other collaboration tools.
55-
Mechanism: When the community is created, it also creates an M365 group, linking to other tools like Outlook (for communication), Planner (for task management), and SharePoint.
56-
**Why**: This group provides a cohesive permission structure that spans all integrated Microsoft 365 services, so members automatically get access to all community content and resources without extra management steps.
5758

58-
### Permissions and Compliance Settings
59-
**Purpose**: To ensure that the community adheres to organizational security policies.
60-
Mechanism: The permissions of the SharePoint site and associated Microsoft 365 group are configured based on community visibility settings (e.g., public, private) and organizational guidelines.
61-
Why: Security, privacy, and compliance are crucial, especially for sensitive discussions. These configurations also ensure that content is retained and deleted according to legal and compliance standards.
59+
**Mechanism**: When the community is created, it also creates an M365 group, linking to other tools like Outlook (for communication), Planner (for task management), and SharePoint.
60+
61+
**Why**: This group provides a cohesive permission structure that spans all integrated Microsoft 365 services, so members automatically get access to all community content and resources without extra management steps. Additionally, the permissions of the associated Microsoft 365 group are configured based on community visibility settings (e.g., public, private) and organizational guidelines, which ensures that the community adheres to organizational security policies.
62+
63+
64+
65+
<br/>
66+
67+
<br/>
68+
69+
# Why hide the resources?
70+
71+
There are several reasons an organization might choose to hide the Resources tab in a Viva Engage community:
6272

63-
### Why hide the resources?
73+
### Prevent Information Overload
6474

6575
When you position Viva Engage Communities in your organisation, you are going to face the questions such as:
6676

6777
* When should I use SharePoint and when Viva Engage?
6878
* What's the difference between Viva Engage Community and Teams chat?
6979
* I already know Teams. What's the added value of Viva Engage?
7080

71-
Seeing links to SharePoint site, SharePoint library, OneNote and Planner in their Viva Engage Community can confuse the users. Some organizations choose to hide this feature to discourage users from storing excessive files within Viva Engage Communities. This helps prevent the creation of additional libraries, which could lead to storage issues over time.
81+
Seeing links to SharePoint site, SharePoint library, OneNote and Planner in their Viva Engage Community can confuse the users. By hiding the links to SharePoint site, SharePoint library, OneNote and Planner, organizations can shift the focus of the community from file-sharing to interactive collaboration, such as conversations, knowledge-sharing, and relationship-building. This aligns with Viva Engage’s purpose of promoting engagement and connection among employees.
82+
83+
<br/>
84+
85+
### Minimize Security and Compliance Risks
86+
87+
Allowing users to upload and share files freely may lead to unintentional sharing of sensitive or confidential information. By hiding the Resources tab, your organization can help reduce these risks and maintain compliance with data governance policies.
88+
89+
<br/>
90+
91+
### Encourage Centralized Document Management
92+
93+
Some organizations choose to hide this feature to discourage users from storing excessive files within Viva Engage Communities. Organizations might prefer that employees use dedicated document storage systems (like SharePoint or OneDrive) This approach centralizes document storage and management and helps prevent the creation of additional libraries, which could lead to storage issues over time.
94+
95+
96+
97+

0 commit comments

Comments
 (0)