removeresources

Author: PowershellScripts

articles/en/Viva/RemoveResources.md

@@ -0,0 +1,50 @@
+---
+layout: page
+title: 'Remove Resources from Viva Engage Community'
+menubar: docs_menu
+hero_image: '/img/IMG_20220521_140146.jpg'
+show_sidebar: false
+hero_height: is-small
+date: '2024-11-03'
+---
+
+TL;DR;
+
+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.
+
+
+<img src="/articles/images/removeresources3.png" width="400">
+
+Go to the Community Settings and deactivate
+
+
+<img src="/articles/images/removeresources.png" width="400">
+
+
+
+<img src="/articles/images/removeresources2.png" width="400">
+
+
+
+# Intro 
+
+
+When a community is created in Viva Engage, the system generates a SharePoint site along with several other resources to support content management, engagement, and security. 
+
+1. SharePoint Site Collection
+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.
+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.
+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.
+
+2. Document Libraries
+Purpose: To organize files and media shared in the community.
+Mechanism: Libraries for documents, images, and other files are created within the associated SharePoint site.
+Why: Organizing media helps ensure content is easily searchable, accessible, and manageable, especially when communities grow in scale and file-sharing increases.
+3. Microsoft 365 Group Creation
+Purpose: The community is also supported by a Microsoft 365 group that grants permissions, handles membership, and offers other collaboration tools.
+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.
+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.
+4. Permissions and Compliance Settings
+Purpose: To ensure that the community adheres to organizational security policies.
+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.
+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.