In the Pinned apps section, click Add apps, and select your new app. The Global (Org-wide default) policy is the one I’m using. You may potentially have multiple policies defined in this section. Select your policy in the list of setup policies. In the Teams apps section in Teams admin, click Setup policies. Step 7: Set the home site as the top (default) app in the left nav of Teams. If you’d like this app (or any of your apps for that matter) to automatically show on the left side, follow these next steps: So far, now your new app will be available for people to add as an app, but it won’t be in the left navigation of Teams by default.
Set mailessentials default site zip file#
Go to the Teams apps section, and click Manage apps.Ĭlick the Upload button, and upload that ZIP file from step 5. Of course, you’ll need to be a Teams Administrator to be able to get there. Start off by heading over to your main Teams admin center. Step 6: Upload your new app (zip file) to Microsoft Teams. After the script runs, it spits out a zip file for you, with the same name as the company name you provided when running the script. There are several pieces of information that you’ll need to provide when running this script, such as the URL to your home site, the name of this “app” the way you want it to appear in Teams, a description, and a couple of icons. Also, I mentioned it in my video, that there was an error the first time I ran it, so I read Wictor Wilen’s blog, and found the solution there. Use this aforementioned link for their detailed instructions and video. This is done via PowerShell, using the instructions in Microsoft’s documentation. Step 5: Add the home site to Teams by Installing Viva Connections. In my example, I just used “Everyone except external users” and gave them Read permissions. Step 4: In the home site’s permissions, make sure you’ve given everyone permission, who you’d like to be able to get to this SharePoint site. (I talked about general navigation, hub, and global nav concepts in the first 12 minutes of the video.) Click the Settings gear at the top right of the site, and choose Global Navigation. Step 3: Go to this home site in the browser. Step 2: Run the PowerShell command Set-SPOHomeSite -HomeSiteUrl The only thing you need to provide in this command, is the URL to your site from step 1. This can be a communication site that already exists, or it can be your root site, but it definitely does need to be created using the Communication Site template. Step 1: Create a communication site that you’ll use as your home site. In the steps below, I’ll put the time in the video at which I do each of these things. I spent about 12 minutes at the beginning of this demo, talking about the hub site / home site / navigation concepts involved. You *can* set your root as your home, but I’m just not doing that here. The URL can be anything, and doesn’t have to be anything special in order to make the site your home site. This is a site with a URL of /sites/home_site. My tenant is, so if I went to that URL, I’d be on the root site. In my example, I’ve created a brand new site using the communication site template, and it is not my tenant’s root site. When it comes to the “home site” concept in SharePoint, it does *not* have to be your root site. We can even set SharePoint to be the default landing page in there! In this post I’ll describe how this works, and there is an hour-long corresponding video at the bottom. Now there is a way to bring your SharePoint home site into Teams, and this functionality is called Viva Connections. Even though there is a SharePoint site is behind the scenes for every Teams team, there has been more and more of a demand to have SharePoint sites come to you where you are working, inside of Microsoft Teams. We use it to chat, to collaborate, hold meetings, and much more. Microsoft Teams has really caught on, and is used by millions of people in their day-to-day work.
0 kommentar(er)
