Note: If you don't see the permissions window, you probably already consented earlier just for yourself.

See this video walkthrough for all the details. If you like, you can spare your end users from having to do this by having one of your Microsoft Teams admins consent to the relevant permissions on behalf of the entire tenant. Step 4 (Optional): Tenant-Wide Consent to Permissionsīy default, each end user needs to complete a one-time permission-approval step when they first open the Skedda app within Microsoft Teams (so that we can identify them). Option 2: If you want the Skedda app to appear in the interface of your organization's users (or a set of them) by default, you can add the Skedda app to an appropriate App Setup Policy that you've created ( video walkthrough). Why isn't it allowed by default, you ask? Well, Skedda has intentionally published its Microsoft Teams app using the 'default block until admin action' option, because it's usually not appropriate for end users to install an app like Skedda until the organization has properly configured it (i.e.

Option 1: If you simply want to permit each user in your organization to manually install the Skedda app in their personal Microsoft Teams interface, log in to the Manage Apps page of your organization's Microsoft Teams Admin Center, search for 'Skedda' in the list of published apps, and change its status to 'Allowed' ( video walkthrough). You have two options, depending on how you want your users to be able to use Skedda inside Microsoft Teams. Step 3: Install the Skedda Microsoft Teams app! Head over to Microsoft to finish the set up.

Install teams app