Skip to content

Commit 7f84473

Browse files
000-507: removeresources
1 parent 0588cd0 commit 7f84473

File tree

1 file changed

+31
-13
lines changed

1 file changed

+31
-13
lines changed

articles/en/Viva/removeresources.md

Lines changed: 31 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -8,13 +8,16 @@ hero_height: is-small
88
date: '2024-11-03'
99
---
1010

11-
TL;DR;
11+
**TL;DR;**
1212

1313
On the right-hand side of your Viva Engage Community you can see the available Resources such as SharePoint Site, Planner and OneNote. With the newest update from Microsoft you can now hide these Resources on the main page of the Viva Engage Community.
1414

1515

1616
<img src="/articles/images/removeresources2.png" width="400">
1717

18+
19+
<br/>
20+
1821
Go to the Community Settings and deactivate
1922

2023

@@ -25,6 +28,8 @@ Go to the Community Settings and deactivate
2528
<img src="/articles/images/removeresources.png" width="400">
2629

2730

31+
<br/>
32+
<br/>
2833

2934
# Intro
3035

@@ -33,21 +38,34 @@ When a community is created in Viva Engage, the system generates a SharePoint si
3338

3439
### SharePoint Site Collection
3540

36-
**Purpose**: This SharePoint site acts as a content repository, providing secure storage and management capabilities for files, images, and documents shared within the Viva Engage community.
41+
**Purpose**: The SharePoint site acts as a content repository, providing secure storage and management capabilities for files, images, and documents shared within the Viva Engage community.
3742

3843
**Mechanism**: A connected SharePoint site is provisioned automatically with document libraries and folders for files, media, and images, enabling a streamlined, collaborative experience where documents can be accessed, edited, and managed directly in context.
3944

40-
Why: This supports file versioning, compliance, data retention, and sharing policies set by the organization. SharePoint also integrates well with OneDrive, allowing individual file and folder sharing.
45+
**Why**: This supports file versioning, compliance, data retention, and sharing policies set by the organization.
46+
47+
### Document Libraries
4148

42-
2. Document Libraries
43-
Purpose: To organize files and media shared in the community.
44-
Mechanism: Libraries for documents, images, and other files are created within the associated SharePoint site.
45-
Why: Organizing media helps ensure content is easily searchable, accessible, and manageable, especially when communities grow in scale and file-sharing increases.
46-
3. Microsoft 365 Group Creation
47-
Purpose: The community is also supported by a Microsoft 365 group that grants permissions, handles membership, and offers other collaboration tools.
49+
**Purpose**: To organize files and media shared in the Viva Engage community.
50+
**Mechanism**: Libraries for documents, images, and other files are created within the associated SharePoint site.
51+
**Why**: Organizing media helps ensure content is easily searchable, accessible, and manageable, especially when communities grow in scale and file-sharing increases.
52+
53+
### Microsoft 365 Group Creation
54+
**Purpose**: The community is also supported by a Microsoft 365 group that grants permissions, handles membership, and offers other collaboration tools.
4855
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.
49-
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.
50-
4. Permissions and Compliance Settings
51-
Purpose: To ensure that the community adheres to organizational security policies.
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.
57+
58+
### Permissions and Compliance Settings
59+
**Purpose**: To ensure that the community adheres to organizational security policies.
5260
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.
53-
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.
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.
62+
63+
### Why hide the resources?
64+
65+
When you position Viva Engage Communities in your organisation, you are going to face the questions such as:
66+
67+
* When should I use SharePoint and when Viva Engage?
68+
* What's the difference between Viva Engage Community and Teams chat?
69+
* I already know Teams. What's the added value of Viva Engage?
70+
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.

0 commit comments

Comments
 (0)