# Teams admin pins hold the top slot while users experiment below

> Turn on user pinning only after the admin pins define the default path, so teams can personalize the surface without burying the core workflow you need adopted first.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/teams-admin-pins-hold-the-top-slot-while-users-experiment-below/
- Source: [learn.microsoft.com](https://learn.microsoft.com/en-us/microsoftteams/teams-app-setup-policies)
- GrowthDex source hub: [Microsoft Learn: Use setup policies to manage, install and pin agents and apps for users](/sources/microsoft-learn-use-setup-policies-to-manage-install-and-pin-agents-and-/)
- Last checked: 2026-06-09T06:09:26.000Z
- Rarity: uncommon
- Budget: low
- Channels: Distribution, Retention, Product
- Stages: teams apps, admin rollout, user pinning, habit formation


## Why this can grow

A rollout can fail in two opposite ways: the interface is too rigid for real teams, or it becomes so flexible that the primary job disappears. Microsoft's setup-policy docs split the difference. Admin pins always take precedence, while user pins can sit below them when user pinning is allowed. That creates a useful growth pattern. The company can lock the first workflow in place, then let local teams adapt the rest around it. The result is not just governance. It is a distribution rail with controlled exploration built in.

## 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. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. 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 admin pins hold the top slot while users experiment below can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Distribution and Retention 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 admin pins always take precedence in Teams, and when user pinning is enabled, user-pinned apps appear below the apps pinned by admins.

## Adjacent tactics in the same lane

- [Teams admin pin path before adoption drift](/growth-ideas/teams-admin-pin-path-before-adoption-drift/) - same source, 2 shared channels, 3 shared stages
- [Teams meeting extension follows the organizer policy](/growth-ideas/teams-meeting-extension-follows-the-organizer-policy/) - same source, 1 shared channel, 1 shared stage
- [Teams mobile policy needs two pins before rollout](/growth-ideas/teams-mobile-policy-needs-two-pins-before-rollout/) - same source, 1 shared channel, 1 shared stage
- [Teams Add pinned apps pane before rollout email](/growth-ideas/teams-add-pinned-apps-pane-before-rollout-email/) - same source, 1 shared channel, 1 shared stage

## Read GrowthDex essays

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

## Related GrowthDex essays

- [The Teams rollout should survive the policy layer](/blog/the-teams-rollout-should-survive-the-policy-layer/) - enterprise rollout, distribution, product-led growth

## Advisory

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