diff --git a/Viva/connections/set-up-admin-center.md b/Viva/connections/set-up-admin-center.md index b37b6fc60d..95024a7a13 100644 --- a/Viva/connections/set-up-admin-center.md +++ b/Viva/connections/set-up-admin-center.md @@ -33,24 +33,24 @@ description: "Learn how to set up Viva Connections in the Microsoft 365 admin ce > > - You must have an Enterprise (E) or Frontline (F) license type to create a Viva Connections experience. > - Viva Connections does not have any requirements to get started. -> - Users with a basic Microsoft 365 subscription (E license) are limited to creating one experience. Users are required to have a Microsoft Viva suite or Viva Communications and Communities license in order to create two or more experiences (up to ten). See [Microsoft Viva plans and pricing](https://www.microsoft.com/microsoft-viva/pricing) for more info. -> - You must have Global Admin or SharePoint admin permissions to access the Microsoft 365 admin center. +> - Users with a basic Microsoft 365 subscription (E license) are limited to creating one experience. Users are required to have a Microsoft Viva suite or Viva Communications and Communities license in order to create two or more experiences (up to ten). For more information, see [Microsoft Viva plans and pricing](https://www.microsoft.com/microsoft-viva/pricing). +> - You must have Global Administrator or SharePoint Administrator permissions to access the Microsoft 365 admin center. > - You must have Teams administrator (or higher) permissions to pin the Viva Connections app in the Teams Admin Center. -> - If your home site is part of a multi-geo tenant outside of the main geo you will need to manage your permissions in the SharePoint Admin Center. +> - If your home site is part of a multi-geo tenant outside of the main geo you will need to manage your permissions in the SharePoint admin center. -[Microsoft Viva Connections](viva-connections-overview.md) is an employee experience app in Microsoft Teams that brings together relevant news, conversations, resources, and tools in one place for every employee. It's built on your current Microsoft 365 ecosystem to help you engage, inform, and empower your workforce. The Viva Connections experience is deployed and accessed in Microsoft Teams. +[Microsoft Viva Connections](viva-connections-overview.md) is an employee experience app in Microsoft Teams that brings together relevant news, conversations, resources, and tools in one place for every employee. It's built on your current Microsoft 365 ecosystem to help you engage, inform, and empower your workforce. The Viva Connections experience is deployed and accessed in Teams. -Use these step-by-step instructions to help you set up and launch Viva Connections experiences in the Microsoft admin center (MAC) for your organization. +Use these step-by-step instructions to help you set up and launch Viva Connections experiences in the Microsoft admin center for your organization. ## Before getting started Setting up Viva Connections only takes a few steps but there are some considerations to think through with other stakeholders at your organization before getting started: -- **Consider the type of experience(s) that are best for your organization**: You can create a stand-alone Viva Connections experience, or you can create a Connections experience that also builds off an existing intranet portal or SharePoint home site. You can create a single Connections experience for your entire organization with dashboard cards targeted to specific audiences (that is, Centralized HR communication), or you can create multiple experiences to meet the needs of distinct audiences (for example, separate content for front-line workers, subsidiaries needing separate content and branding, etc.). Keep in mind that if you have multiple experiences with overlapping content, each experience needs to be updated separately. Learn more on how to plan, build, and launch Viva Connections. +- **Consider the type of experience(s) that are best for your organization**: You can create a stand-alone Viva Connections experience, or you can create a Connections experience that also builds off an existing intranet portal or SharePoint home site. You can create a single Connections experience for your entire organization with dashboard cards targeted to specific audiences (that is, centralized HR communication), or you can create multiple experiences to meet the needs of distinct audiences (for example, separate content for frontline workers, subsidiaries needing separate content and branding, and so on). Keep in mind that if you have multiple experiences with overlapping content, each experience needs to be updated separately. Learn more on how to plan, build, and launch Viva Connections. - **Decide which audiences should be associated with each experience**: You can create more than one Connections experiences if your organization has a need for different employee experiences for distinct audiences. Decide which experiences should be associated with specific audiences. You want to consider the order of experiences that should be seen for audiences that may belong to more than one experience. -- **Think about who should have owner permissions to each experience**: [Owners have full permissions to edit the experience](edit-viva-home.md) and manage access for others. As a best practice, it’s recommended that each experience has a minimum of two owners assigned to it. +- **Think about who should have owner permissions to each experience**: [Owners have full permissions to edit the experience](edit-viva-home.md) and manage access for others. As a best practice, we recommend that each experience has a minimum of two owners assigned to it. - **Pick an icon and name for your app**: Choose an app icon and name to apply to your entire Connections app. This icon and label will display as an app in the Teams app bar. Consider what the right branding elements are for your organization. You want to pick a name that aligns with your organization’s brand, and that’s also meaningful and recognizable to viewers. @@ -62,7 +62,7 @@ Setting up Viva Connections only takes a few steps but there are some considerat 1. Navigate to [admin.microsoft.com](https://admin.microsoft.com/Adminportal/Home#/homepage) and sign in with your credentials. 2. Select **Setup** and under featured collections, select **Microsoft Viva**. - :::image type="content" source="../media/connections/set-up-admin-center/microsoft-viva-option.png" alt-text="Screenshot showing how to navigate to the Microsoft Viva admin center." lightbox="../media/connections/set-up-admin-center/microsoft-viva-option.png"::: + :::image type="content" source="../media/connections/set-up-admin-center/microsoft-viva-option.png" alt-text="Screenshot that shows how to navigate to the Microsoft Viva admin center." lightbox="../media/connections/set-up-admin-center/microsoft-viva-option.png"::: 3. Select **Viva Connections** to open the Viva Connections admin center. 4. The Viva Connections admin center opens. If you already have a SharePoint home site (intranet portal), Viva Connections will display it as an experience automatically. @@ -77,19 +77,19 @@ Create an all-encompassing Connections experience for the entire organization, o > > - Organizations are limited to creating a maximum of ten Viva Connections experiences overall per tenant. > - A Microsoft Viva Suite license or Viva Communications and Communities license is required to create more than one Viva Connections experience. Check the [current license for your organization in billing under licenses](https://www.microsoft.com/microsoft-viva/pricing). -> - You must have Global admin permissions, SharePoint admin permissions, or higher to access the MAC. -> - If this is the first time you're setting up Viva Connections, it's recommended you pin the app in Teams. +> - You must have Global Administrator or SharePoint Administrator permissions to access the Microsoft 365 admin center. +> - If this is the first time you're setting up Viva Connections, we recommend that you pin the app in Teams. ### Step 1: Create a new experience -Admins are able to create multiple standalone experiences well as intranet home sites having their own Viva Connections experience. As a result, there are now two options for creating a new experience: +Admins are able to create multiple standalone experiences as well as intranet home sites having their own Viva Connections experience. As a result, there are now two options for creating a new experience: > **A. Creating a Connections experience**: This option is the fastest way to get started. It creates a standalone, out-of-the-box Connections experience as an app in Teams without the need for an existing intranet portal. A special site container will be created where the dashboard, resources, and overall Viva home experience are hosted and sourced from. Owners can then begin adding their own content. An intranet portal can be added at any time and designated as a home site.

-> **B. Build from an existing intranet portal**: This option is ideal for organizations that already have a SharePoint communications site and would like to use their own content, or would like to add an intranet portal that includes Connections components that can easily be extended to the Web. This option creates a new Connections experience and automatically designates the communications site as a home site (intranet portal) that displays navigational elements, and shares permissions. +> **B. Build from an existing intranet portal**: This option is ideal for organizations that already have a SharePoint communications site and would like to use their own content, or would like to add an intranet portal that includes Connections components that can easily be extended to the web. This option creates a new Connections experience and automatically designates the communications site as a home site (intranet portal) that displays navigational elements, and shares permissions. - :::image type="content" source="../media/connections/set-up-admin-center/create-new-viva-connections-experience.png" alt-text="Screenshot showing options for creating a Viva Connections experience." lightbox="../media/connections/set-up-admin-center/create-new-viva-connections-experience.png"::: + :::image type="content" source="../media/connections/set-up-admin-center/create-new-viva-connections-experience.png" alt-text="Screenshot that shows options for creating a Viva Connections experience." lightbox="../media/connections/set-up-admin-center/create-new-viva-connections-experience.png"::: #### Create a Connections experience @@ -106,7 +106,7 @@ This option is ideal if your organization doesn't have an existing intranet port 3. Give the new experience a name, add a description, decide the settings, and then select **Next**. > [!NOTE] - > The name given to the experience in the MAC will also display for owners and members who help manage and edit experiences. + > The name given to the experience in the Microsoft admin center will also display for owners and members who help manage and edit experiences. 4. After reviewing your settings, select **Create experience**. @@ -115,7 +115,7 @@ This option is ideal if your organization doesn't have an existing intranet port #### Build from an existing intranet portal -If your organization has an existing intranet portal, then this option allows you to use the existing content, or add an intranet portal that includes Connections components that can easily be extended to the Web. +If your organization has an existing intranet portal, then this option allows you to use the existing content, or add an intranet portal that includes Connections components that can easily be extended to the web. 1. Select **+ Create new**, displayed on top of the list of experiences. @@ -128,9 +128,9 @@ If your organization has an existing intranet portal, then this option allows yo 3. Paste the URL of your SharePoint communication site in the **URL of the communication site you want to use** field. > [!NOTE] - > The name given to the experience in the MAC will also display for owners and members who help manage and edit experiences. + > The name given to the experience in the Microsoft admin center will also display for owners and members who help manage and edit experiences. - :::image type="content" source="../media/connections/set-up-admin-center/set-intranet-portal-pr.png" alt-text="The screenshot of this diagram presents the option to build a Connections experience from an existing intranet portal." lightbox="../media/connections/set-up-admin-center/set-intranet-portal-pr.png"::: + :::image type="content" source="../media/connections/set-up-admin-center/set-intranet-portal-pr.png" alt-text="Screenshot that presents the option to build a Connections experience from an existing intranet portal." lightbox="../media/connections/set-up-admin-center/set-intranet-portal-pr.png"::: 4. After reviewing your settings, select **Create experience**. @@ -139,7 +139,7 @@ If your organization has an existing intranet portal, then this option allows yo #### Choose the landing destination in the Viva Connections app -Customers building from an existing intranet portal are able to choose the landing destination for audiences in Teams via PowerShell command. (See Choose the default landing experience for Viva Connections desktop for more info). +Customers building from an existing intranet portal are able to choose the landing destination for audiences in Teams via PowerShell command. For more information, see Choose the default landing experience for Viva Connections desktop. PowerShell functionality is limited initially as follows: @@ -147,11 +147,11 @@ PowerShell functionality is limited initially as follows: | **Command** | **Result** | |----|----| | **Get-SPOHomeSite** | Returns the single home site URL.

With multiple Viva Connections home sites, a warning message and the first Viva Connection home site from the list will be shown. -| **Set-SPOHomeSite** | 1. Initially it will continue supporting a single home site setup. Setting up more home sites can be done in the MAC. Support for setting up multiple home sites will be supported at a later stage.

2. It updates the Viva Connections default landing destination (Viva Connections, home site, or draft status for a home site). This functionality will continue getting support in multiple Viva Connection home sites. The cmdlet can be run with the home site URL to set the landing destination. -| **Remove-SPOHomeSite** | This won't be supported initially for multiple home sites customers, but the MAC will support this operation. Users attempting to use the cmdlet will receive an error message and be redirected to the MAC. | +| **Set-SPOHomeSite** | 1. Initially it will continue supporting a single home site setup. Setting up more home sites can be done in the Microsoft admin center. Support for setting up multiple home sites will be supported at a later stage.

2. It updates the Viva Connections default landing destination (Viva Connections, home site, or draft status for a home site). This functionality will continue getting support in multiple Viva Connection home sites. The cmdlet can be run with the home site URL to set the landing destination. +| **Remove-SPOHomeSite** | This won't be supported initially for multiple home sites customers, but the Microsoft admin center will support this operation. Users attempting to use the cmdlet will receive an error message and be redirected to the Microsoft admin center. | > -#### When to use a separate experience vs dashboard card-level targeting +#### When to use a separate experience vs. dashboard card-level targeting Depending on the size of your organization, and the information to communicate, you may decide to create a separate experience for each audience you wish to target or use card-level targeting in your dashboard to provide a targeted experience. There are scenarios in which you may choose one or the other. For information on these scenarios, see [Scenarios for creating additional Viva Connections experiences](#scenarios-for-creating-additional-viva-connections-experiences). @@ -180,7 +180,7 @@ Assign two or more owners to each experience so that they have full access to [e 2. Select the **Permissions** tab from the settings panel. The owners assigned to the experience will display here. > [!NOTE] -> If your home site is part of a multi-geo tenant outside of the main geo you will need to manage your permissions in the SharePoint Admin Center. +> If your home site is part of a multi-geo tenant outside of the main geo you will need to manage your permissions in the SharePoint admin center. 3. Select **Add**. 4. Enter the names of the people you want to assign as owners to this experience in the search bar. @@ -198,10 +198,10 @@ Decide which Azure Active Directory security groups or Microsoft 365 groups shou Audience targeting can be set up by doing either of the following tasks: -1. Assigning one or more Azure Active Directory security groups or Microsoft 365 groups to the experience (This is the most common scenario). -2. Assigning license-level filtering, and choosing if frontline workers (F-license holders) or non-frontline workers should be targeted. (This option has been introduced to account for a scenario where a targeted experience for frontline and information workers is needed.) +1. Assigning one or more Azure Active Directory security groups or Microsoft 365 groups to the experience. Note that this is the most common scenario. +2. Assigning license-level filtering, and choosing if frontline workers (F-license holders) or non-frontline workers should be targeted. Note that this option has been introduced to account for a scenario where a targeted experience for frontline and information workers is needed. -In this example scenario, Contoso Retail wants to target all sales frontline workers for a specific Connections experience. However, they have an Azure Active Directory (Azure AD) group for ‘Contoso Sales All’ that includes sales directors and higher who are non-frontline workers. To set up the audience targeting, the Azure AD group ‘Contoso Sales All’ license filtering option should be set to **frontline workers**. This setting will filter down the experience to only members of the ‘Contoso Sales All’ group who are also frontline workers (F-license holders). If the end user selects both options, an ‘AND’ operation is created, and the end user has to satisfy both the group and the license filtering criteria to access the experience. +In this example scenario, Contoso Retail wants to target all sales frontline workers for a specific Connections experience. However, they have an Azure Active Directory (Azure AD) group for "Contoso Sales All" that includes sales directors and higher who are non-frontline workers. To set up the audience targeting, the Azure AD group "Contoso Sales All" license filtering option should be set to **frontline workers**. This setting will filter down the experience to only members of the "Contoso Sales All" group who are also frontline workers (F-license holders). If the end user selects both options, an `AND` operation is created, and the end user has to satisfy both the group and the license filtering criteria to access the experience. Users who have already designated audiences for their experiences can use the following steps to manage their audiences: @@ -231,9 +231,9 @@ If your organization has multiple experiences, some audiences may belong to more #### Example of how ordering works with multiple experiences -:::image type="content" source="../media/connections/set-up-admin-center/how-ordering-works-with-multiple-experiences.png" alt-text="Screenshot of the screen that describes how ordering works with multiple experiences." lightbox="../media/connections/set-up-admin-center/how-ordering-works-with-multiple-experiences.png"::: +:::image type="content" source="../media/connections/set-up-admin-center/how-ordering-works-with-multiple-experiences.png" alt-text="Screenshot that describes how ordering works with multiple experiences." lightbox="../media/connections/set-up-admin-center/how-ordering-works-with-multiple-experiences.png"::: -In this example (in the screenshot), there are two Connections experiences for an organization. Both experiences have been enabled and can be seen by viewers. +The previous screenshot shows two Connections experiences for an organization. Both experiences have been enabled and can be seen by viewers. The experience named **Contoso 123** is scoped to workers at the organization who are members of the CM (Contoso Members) group. The **comm1** experience is targeted to all employees at the organization and provides information targeted to everyone. @@ -247,9 +247,9 @@ If the example organization creates another experience scoped to a subset of the 2. Drag and drop the handles next to each experience to reorder as desired. 3. Select **Save** when you're done. - :::image type="content" source="../media/connections/set-up-admin-center/set-order-of-experiences.png" alt-text="Screenshot of the screen on which you set the order of experiences." lightbox="../media/connections/set-up-admin-center/set-order-of-experiences.png"::: + :::image type="content" source="../media/connections/set-up-admin-center/set-order-of-experiences.png" alt-text="Screenshot that shows how you can set the order of experiences." lightbox="../media/connections/set-up-admin-center/set-order-of-experiences.png"::: - :::image type="content" source="../media/connections/set-up-admin-center/set-order-2.png" alt-text="Screenshot of the screen that shows order of experiences." lightbox="../media/connections/set-up-admin-center/set-order-2.png"::: + :::image type="content" source="../media/connections/set-up-admin-center/set-order-2.png" alt-text="Screenshot that shows the order of experiences." lightbox="../media/connections/set-up-admin-center/set-order-2.png"::: ### Step 5: Configure the dashboard @@ -273,13 +273,13 @@ If you need to update the experience, you can also return it to **Draft** status > [!NOTE] > > - The Viva Connections app only needs to be pinned to Teams once after the creation of your first experience, unless you are pinning by policy. -> - If you are pinning by a policy, revisit your pinning policy to make sure the Viva Connections app is pinned correctly for intended users every time you add a new experience. See Manage app setup policies for more info. -> - Teams administrator (or higher) permissions are required. +> - If you are pinning by a policy, revisit your pinning policy to make sure the Viva Connections app is pinned correctly for intended users every time you add a new experience. For more information, see Manage app setup policies. +> - Teams Administrator (or higher) permissions are required. -Viva Connections creates web parts for organizations who build off existing intranet portals, or home sites which can be accessed via Microsoft Teams. The app is auto enabled by default, but to make Viva Connections easily discoverable, it’s recommended to pin the app. Once the app is pinned, your organization’s icon and custom app name will appear in the Teams app bar. +Viva Connections creates web parts for organizations who build off existing intranet portals, or home sites which can be accessed via Teams. The app is auto enabled by default, but to make Viva Connections easily discoverable, we recommend that you pin the app. Once the app is pinned, your organization’s icon and custom app name will appear in the Teams app bar. > [!NOTE] -> Pre-pinning the Viva Connections app doesn't change the Microsoft Teams experience and doesn't automatically open the app in Teams. Pre-pinning makes it easier to discover and use the Viva Connections app. +> Pre-pinning the Viva Connections app doesn't change the Teams experience and doesn't automatically open the app in Teams. Pre-pinning makes it easier to discover and use the Viva Connections app. 1. Navigate to **Teams admin center > Teams apps > Setup policies**. 2. Select **Global (Org-wide default)** (this is the default policy for all users). @@ -296,26 +296,26 @@ Learn more about [Adding the Viva Connections app in the Teams Admin Center](add The following settings are available in the settings panel: -1. **Open in Teams**: Open this experience in the Teams app. -2. **Analytics**: Download data for overall traffic, usage, and usage by platform for the selected experience in an Excel spreadsheet (Learn more about [Usage data for Viva Connections](viva-connections-analytics.md)). -3. **Delete**: Permanently delete the selected Viva Connections experience. -4. **General tab**: Provides settings to manage the selected experience. -5. **Audience tab**: Create audiences to associate with the selected experience. -6. **Permissions tab**: Assign owners who have permission to edit content in the selected experience. -7. **Experience name**: Edit the name of the selected experience (visible only to administrators in the MAC). -8. **Status**: Indicates if the status of the selected experience is **Draft** or **Enabled**. -9. **Experience description**: A brief description of the experience for administrators (not commonly seen by users). -10. **URL**: Location of the intranet home site (if one has been added) or the special site container (if the experience wasn't created from an existing intranet portal). -11. **License type**: Which license type the experience has been scoped for (for example, frontline workers, enterprise, or all). -12. **Creation date and details**: Information on the creation of the experience. -13. **Time zone**: What time zone the experience is set for. -14. **Default language**: What default language the experience is set as. +- **Open in Teams**: Open this experience in the Teams app. +- **Analytics**: Download data for overall traffic, usage, and usage by platform for the selected experience in an Excel spreadsheet. Learn more about [Usage data for Viva Connections](viva-connections-analytics.md). +- **Delete**: Permanently delete the selected Viva Connections experience. +- **General tab**: Provides settings to manage the selected experience. +- **Audience tab**: Create audiences to associate with the selected experience. +- **Permissions tab**: Assign owners who have permission to edit content in the selected experience. +- **Experience name**: Edit the name of the selected experience (visible only to administrators in the Microsoft admin center). +- **Status**: Indicates if the status of the selected experience is **Draft** or **Enabled**. +- **Experience description**: A brief description of the experience for administrators (not commonly seen by users). +- **URL**: Location of the intranet home site (if one has been added) or the special site container (if the experience wasn't created from an existing intranet portal). +- **License type**: Which license type the experience has been scoped for (for example, frontline workers, enterprise, or all). +- **Creation date and details**: Information on the creation of the experience. +- **Time zone**: What time zone the experience is set for. +- **Default language**: What default language the experience is set as. ### Delete a Connections experience > [!IMPORTANT] > -> Deleting a Viva Connections experience will remove it from your list of experiences. However the site will still remain available under the list of active sites in the SharePoint Admin Center (SPAC). +> Deleting a Viva Connections experience will remove it from your list of experiences. However the site will still remain available under the list of active sites in the SharePoint admin center (SPAC). > > - If the experience was tied to an intranet portal-based experience, the home site designation will be removed and the site will become a regular SharePoint communication site again. > - If the experience was a standalone Connections experience, it will be removed from the list but the special site container, and the content, will still be available through the active sites in SPAC. @@ -331,7 +331,7 @@ The following settings are available in the settings panel: ### Add a SharePoint home site after setting up a Connections experience - :::image type="content" source="../media/connections/set-up-admin-center/setting-home-site-after-setting-up-connections-experience.png" alt-text="Screenshot showing an example of a SharePoint home site after set up." lightbox="../media/connections/set-up-admin-center/setting-home-site-after-setting-up-connections-experience.png"::: + :::image type="content" source="../media/connections/set-up-admin-center/setting-home-site-after-setting-up-connections-experience.png" alt-text="Screenshot that shows an example of a SharePoint home site after set up." lightbox="../media/connections/set-up-admin-center/setting-home-site-after-setting-up-connections-experience.png"::: > [!IMPORTANT] > @@ -340,13 +340,13 @@ The following settings are available in the settings panel: Connections and home sites (also referred to as intranet portals) are two complementary methods to creating powerful employee experiences that can be viewed on the web and in Teams. [Learn more about how Connections and homes sites work together](/viva/connections/viva-connections-overview#how-sharepoint-home-sites-and-viva-connections-work-together). -A home site is not required to set up Viva Connections, but it’s recommended that you add one while setting up Connections to reduce the risk of needing to manually copy content between experiences in some cases. [Learn more about how to plan and build a home site](/viva/connections/home-site-plan). +A home site is not required to set up Viva Connections, but we recommend that you add one while setting up Connections to reduce the risk of needing to manually copy content between experiences in some cases. [Learn more about how to plan and build a home site](/viva/connections/home-site-plan). Take the following scenario: An organization that does not have an existing intranet home site creates a Viva Connections experience using the standalone out-of-the-box option during creation. Over a year the organization populates the experience with content. A year later, the organization begins to develop a SharePoint communication site for their content and wants to set the SharePoint home site with a Viva Connections experience so their employees can access the content on SharePoint as well as in the Viva Connections app in Teams. -The organization would need to create a new experience, this time building their experience from an existing intranet portal (i.e. the SharePoint communication site). Once the new experience has been fully set up (e.g. permissions assigned, audiences designated, order), the content from the initial standalone experience will need to be recreated in the new experience built from the intranet home site. Once the content from the old experience has been manually recreated over to the new experience, admins would need to put the old experience into a draft status or delete it and enable the new experience. This would direct visitors to the new experience where they can access the content from the Viva Connections app in Teams or SharePoint. +The organization would need to create a new experience, this time building their experience from an existing intranet portal (for example, the SharePoint communication site). Once the new experience has been fully set up (for example, permissions assigned, audiences designated, and order), the content from the initial standalone experience will need to be recreated in the new experience built from the intranet home site. Once the content from the old experience has been manually recreated over to the new experience, admins would need to put the old experience into a draft status or delete it and enable the new experience. This would direct visitors to the new experience where they can access the content from the Viva Connections app in Teams or SharePoint. #### To add a home site after you've set up a Connections experience @@ -355,7 +355,7 @@ The organization would need to create a new experience, this time building their If your organization doesn’t have any custom Connections content in Teams yet, you do not need to manually copy content. Instead, you can **Save** the home site and enable the experience. - :::image type="content" source="../media/connections/set-up-admin-center/copy-content-to-home-site-small.png" alt-text="Screenshot showing an example of a SharePoint home site." lightbox="../media/connections/set-up-admin-center/copy-content-to-home-site.png"::: + :::image type="content" source="../media/connections/set-up-admin-center/copy-content-to-home-site-small.png" alt-text="Screenshot that shows an example of a SharePoint home site." lightbox="../media/connections/set-up-admin-center/copy-content-to-home-site.png"::: 3. For organizations who have already set up dashboard and navigation content in Teams, keep the home site in **Draft mode** until the content has been copied to the home site in SharePoint. @@ -364,16 +364,16 @@ The organization would need to create a new experience, this time building their Follow these instructions if your organization already has custom Connections dashboard and navigation content set up from Teams that you want to preserve when you add a home site. > [!NOTE] -> You'll need SharePoint admin permissions or higher to complete the following steps. +> You'll need SharePoint Administrator permissions or higher to complete the following steps: 1. Keep the new home site in **Draft mode** until content has been copied to the home site in SharePoint. 2. Navigate to SharePoint and go to the home site. Next go to **Settings**. 3. Copy dashboard content from Teams to SharePoint. To set up the dashboard from the home site, go to **Set up Viva Connections > Create dashboard**. Preview and then **Publish** the dashboard when it’s ready to be shared with others. - :::image type="content" source="../media/connections/set-up-admin-center/sharepoint-settings.png" alt-text="Screenshot showing the setting options in SharePoint." lightbox="../media/connections/set-up-admin-center/sharepoint-settings-big.png"::: + :::image type="content" source="../media/connections/set-up-admin-center/sharepoint-settings.png" alt-text="Screenshot that shows the setting options in SharePoint." lightbox="../media/connections/set-up-admin-center/sharepoint-settings-big.png"::: 4. Copy content in the navigation column in the Resources section to global navigation in SharePoint. Go to **Global navigation > Enable** and then customize the navigational links. These links will automatically populate the navigation column in the Resources section of the Connections experience. -5. After all the content you want to preserve has been copied to the home site in SharePoint, navigate back to the Connections experience in the MAC and turn the **Draft mode** toggle off and then select **Save**. +5. After all the content you want to preserve has been copied to the home site in SharePoint, navigate back to the Connections experience in the Microsoft admin center and turn the **Draft mode** toggle off and then select **Save**. ## Frequently Asked Questions