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.
Why this can grow a startup
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.
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.
Source-reported evidence
Source: Microsoft Learn: Use setup policies to manage, install and pin agents and apps for users · Browse Microsoft Learn: Use setup policies to manage, install and pin agents and apps for users tactics
Admin pins stay on top while user pins are placed underneath them when user pinning is turned on.
Attributed to the cited source; GrowthDex has not independently verified it. Use this as context, not as a forecast, benchmark, or recommended target.
Evidence scope: claims and metrics are attributed to the linked source; GrowthDex has not independently replicated the reported result. Check the original context and validate fit before applying it. Read the evidence methodology.
When to use it
Use this when Distribution, Retention, Product is relevant to teams apps, admin rollout, user pinning and you can run a bounded test with a low budget.
When not to use it
Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.
How to do it
- Choose one target segment and define the exact next action this tactic should prompt.
- Adapt the tactic to Distribution and Retention, using evidence from Microsoft Learn: Use setup policies to manage, install and pin agents and apps for users as context—not as a promised result.
- Record a baseline for: Target users who complete the tactic’s intended next action. Set a guardrail that would make you pause the test.
- Run a narrow pilot and choose a test window that fits the normal decision or use cycle; do not scale before you have observed the full cycle.
- Compare the signal with its baseline. Scale only if the intended action improves without crossing the guardrail; otherwise revise one variable or stop and record what you learned.
Compare a stack for your situation
Compare source-backed tactics against your product, stage, budget and channel strengths, then choose one experiment to test.
Explore the context
Did you launch this experiment?
Report a launch to help us understand which growth ideas founders put into practice.
Apply this with an operator
Connect activation, customer value, retention, and referral into one measurable loop.
SOURCE HUB
More tactics from Microsoft Learn: Use setup policies to manage, install and pin agents and apps for users
Explore related GrowthDex examples and evidence connected to Microsoft Learn: Use setup policies to manage, install and pin agents and apps for users.
Open Microsoft Learn: Use setup policies to manage, install and pin agents and apps for users source hub