# Teams default install scope matches the first job

> Set the default install scope to the first place the user should get value, so Teams recommends the right surface instead of forcing them through a scope choice they do not understand yet.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/teams-default-install-scope-matches-the-first-job/
- Source: [learn.microsoft.com](https://learn.microsoft.com/en-us/microsoftteams/platform/concepts/deploy-and-publish/add-default-install-scope)
- GrowthDex source hub: [Microsoft Learn: Configure default options for your app](/sources/microsoft-learn-configure-default-options-for-your-app-learn-microsoft-c/)
- Last checked: 2026-06-09T02:07:48.000Z
- Rarity: rare
- Budget: free
- Channels: Onboarding, Activation, Product
- Stages: teams apps, install flow, scope strategy, activation


## Why this can grow

A lot of Teams apps lose momentum on the first screen because the buyer has to decide where the app belongs before they know what the app is good for. Microsoft's install-scope docs make the tradeoff plain. You can set one default install scope, Teams labels that scope as recommended, and the resulting install flow becomes quicker and more straightforward. That is not just a manifest convenience. It is a positioning choice. The best default scope usually points at the first job you want completed, not the broadest surface your app happens to support.

## Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. My bias is to treat this as a small market test first. Make the audience narrow, make the promise concrete, and let the first real response decide whether it deserves more work. For activation, the useful question is not whether users liked the page. It is whether they got to the first meaningful win faster. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where teams default install scope matches the first job can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Onboarding and Activation channel.
3. Use the evidence from learn.microsoft.com to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## Source-backed example

Microsoft says apps can set one `defaultInstallScope` to `personal`, `team`, `groupChat`, or `meetings`, and the configured scope appears as the recommended option in the install flow.

## Adjacent tactics in the same lane

- [Slack onboarding starts at the first invocation context](/growth-ideas/slack-onboarding-starts-at-the-first-invocation-context/) - 3 shared channels, 1 shared stage
- [Figma Community playground file before broad promotion](/growth-ideas/figma-community-playground-file-before-broad-promotion/) - 2 shared channels, 1 shared stage
- [Manual empty-state concierge onboarding](/growth-ideas/manual-empty-state-concierge-onboarding/) - 2 shared channels, 1 shared stage
- [Manual chat onboarding before self-serve](/growth-ideas/manual-chat-onboarding-before-self-serve/) - 2 shared channels, 1 shared stage

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The Teams app should meet the work before the help doc](/blog/the-teams-app-should-meet-the-work-before-the-help-doc/) - onboarding, product-led growth, brand trust

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.