Try itStart free trialENDE

Deploy the Teams app

To make TeamsDashboard appear directly in Microsoft Teams, upload an app package to your organization's app catalog once. The package is already set to your organization – there is nothing to configure or edit.

Time required: about 5 minutes. Required role: Teams administrator or Global Administrator.

The app also works without this step – at teamsdashboard.com/app/ in the browser. Deploying it in Teams is a convenience, not a requirement.

Step by step

  1. 1Download the package

    Sign in to the customer portal and open the Teams app tab. The button Download Teams package delivers a ZIP file – please do not unzip and do not rename it.

  2. 2Upload it in the Teams admin center

    Open the Teams admin center and go to Teams apps → Manage apps. There, in the menu Actions → Upload new app, select the ZIP file.

    The app then appears in the list as an app provided by your organization.

  3. 3Define who may use the app

    Two management models differ here:

    • App-centric management (the standard since 2025, to which tenants are migrated automatically): click TeamsDashboard in the app list and manage access directly on the app under Users and groups.
    • Classic app permission policies (only on tenants not yet migrated): access is controlled under Teams apps → Permission policies.

    You can tell which model is active right from the interface: if the Users and groups section is missing on the app, your tenant has not been migrated yet.

  4. 4Optional: pin it to the Teams rail

    Under Teams apps → Setup policies you can pin TeamsDashboard so that it is permanently visible in the left rail for your employees.

  5. 5Wait and verify

    The catalog entry is usually available after a few hours. Changes to availability (policies, users and groups) can take longer to reach all clients. Restarting the Teams client speeds up the display.

Individual installation for testing

If you want to try the app just for yourself first, you can do so without the admin center: in the Teams client go to Apps → Manage your apps → Upload an app → Upload a custom app.

If this menu item is missing, uploading custom apps is disabled in your app setup policy. That is by far the most common reason – not an error in the package.

Updating

For a new version, simply download the current package from the customer portal and upload it again in the admin center. Since the app ID stays the same, Teams replaces the existing app: policies and pins are preserved, no uninstall is needed.

With the first package of this generation, the app's sign-in settings change. Microsoft treats this as a change requiring consent – an update consent may therefore appear once, which an administrator confirms. This is expected and not an error.

Before you start

Without the one-time Microsoft consent and the data processing agreement, the app shows no data – even if it sits cleanly in the catalog. An administrator grants consent via the personal consent link from the onboarding email and signs the contract in the customer portal: → Admin onboarding · → Customer portal.

If the app does not show up or stays empty: → Troubleshooting · → Support