Notion Any workspace scope before Marketplace push
Choose Any workspace when you create the public connection if Marketplace distribution is even a medium-term goal, because a Selected workspaces connection can never be promoted into the shelf later.
Why this can grow a startup
A lot of distribution mistakes happen before the listing exists. Notion makes installation scope part of the connection itself, not a later marketing toggle. The Marketplace docs and public-connections guide are blunt about the consequence: only Any workspace connections can be listed, the scope is fixed at creation, and if you pick Selected workspaces only you need a new connection later. That changes the growth question. The operator is not deciding whether to launch publicly today. The operator is deciding whether the current connection should preserve that option at all. If the team wants design partners first, fine. Keep the rollout small. But keep the underlying connection eligible so the learning can graduate without a rebuild.
Source-backed example
Notion says only public connections with an Any workspace installation scope are Marketplace-eligible, and says Selected workspaces only cannot be changed later and requires creating a new connection if you later want Marketplace distribution.
Source-reported evidence
Source: Notion Docs: List on the Marketplace
Only Any workspace public connections can be listed on the Notion Marketplace, and installation scope cannot be changed after creation.
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 Marketplaces, Onboarding, Product Strategy is relevant to notion public connections, installation scope, marketplace eligibility and you can run a bounded test with a free 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 Marketplaces and Onboarding, using evidence from Notion Docs: List on the Marketplace 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
Choose product surfaces that compound distribution without hiding weak activation or retention.