# The Notion connection should earn the first workspace > Why Notion public-connection growth depends on scope choice, template-led auth, page-picker reality, post-install seeding, and owned-domain link previews. - Canonical HTML: https://growth.iangoh.com/blog/the-notion-connection-should-earn-the-first-workspace/ - Published: 2026-06-09 - Updated: 2026-06-09T10:06:53.000Z - Categories: product-led growth, marketplaces, brand trust - Niches: SaaS, AI products, creator tools, operations software, workflow tools, community-led growth ## On this page - Marketplace optionality is decided earlier than most teams think - The auth flow should create something real - Permission reality is part of onboarding quality - Blank workspaces do not deserve blank outcomes - Owned links can become habit surfaces - Where this matters ## Start with these related tactics - [Notion Any workspace scope before Marketplace push](/growth-ideas/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. - [Notion auth template choice before empty install](/growth-ideas/notion-auth-template-choice-before-empty-install/): Offer a template during OAuth when the first useful setup is easier to duplicate than explain, so the user arrives in a working workspace instead of an empty permission grant. - [Notion page picker full access before rollout video](/growth-ideas/notion-page-picker-full-access-before-rollout-video/): Base the rollout around pages the champion fully owns before you record the install video, because Notion's page picker only shows pages and databases the user has full access to share. A lot of Notion integrations still treat installation as the finish line. Get the OAuth button working. Put the listing live. Let the user figure out the rest. That is usually the wrong shape. The connection should earn the first workspace. ## Marketplace optionality is decided earlier than most teams think [Notion Any workspace scope before Marketplace push](/growth-ideas/notion-any-workspace-scope-before-marketplace-push/) is the first place I would slow down. Notion makes installation scope part of the connection itself. If the team chooses Selected workspaces only, that connection will never become Marketplace-eligible later. This sits close to [Google Chat app audience choice before marketplace push](/growth-ideas/google-chat-app-audience-choice-before-marketplace-push/). Both platforms punish teams that confuse a pilot decision with a permanent distribution shape. ## The auth flow should create something real [Notion auth template choice before empty install](/growth-ideas/notion-auth-template-choice-before-empty-install/) is the cleaner opening move. If the first useful setup is easier to duplicate than describe, let the user duplicate it during OAuth and land in a real page instead of a blank permission state. I would read that beside [Notion template linked-content audit before submit](/growth-ideas/notion-template-linked-content-audit-before-submit/). Different surface, same obligation. The copied workspace should still work after the magic wears off. ## Permission reality is part of onboarding quality [Notion page picker full access before rollout video](/growth-ideas/notion-page-picker-full-access-before-rollout-video/) is the operational rule. A builder's demo workspace often has cleaner permissions than the buyer's real one. If the page picker cannot show the page the video promised, the install suddenly feels broken. That belongs with [Slack Marketplace review rehearsal on a non-dev workspace](/growth-ideas/slack-marketplace-review-rehearsal-on-a-non-dev-workspace/). Distribution surfaces usually fail in the permissions layer before they fail in the product layer. ## Blank workspaces do not deserve blank outcomes [Notion post-install database seeding before manual sharing](/growth-ideas/notion-post-install-database-seeding-before-manual-sharing/) is the move I like most here. If the product needs a board, queue, or operating system, the connection should build that system right after auth instead of waiting for the user to assemble it from scratch. This is the same practical instinct behind [onboarding discovery bundle for AI-native sites](/growth-ideas/onboarding-discovery-bundle-for-ai-native-sites/). Good onboarding provisions the useful structure first and explains it second. ## Owned links can become habit surfaces [Notion owned-domain link preview before generic embed](/growth-ideas/notion-owned-domain-link-preview-before-generic-embed/) is the growth move that compounds after setup. A generic embed only proves the URL exists. A live unfurl can carry status, context, and product proof into the collaboration stream where people are already working. I would pair that with [root skill.md for product capability discovery](/growth-ideas/root-skill-md-for-product-capability-discovery/) and [publish llms.txt for agent retrieval](/growth-ideas/publish-llms-txt-for-agent-retrieval/). Different formats, same lesson: make the product legible in the places where people and machines already decide what to trust. ## Where this matters This cluster is strongest for workflow SaaS, AI copilots, creator systems, CRM overlays, research tools, internal ops software, and any product that needs to move from one user's test into a repeatable team habit. If I were testing this in one week, I would choose the right installation scope, add one auth template, record the flow with a real champion account, auto-create one useful database after install, and turn one owned URL into a live link preview. Then I would watch whether the second user gets value faster than the first. For founders tightening the install path, workspace proof, and trust surfaces around a Notion-connected product, the advisory CTA is here: [work with Ian Goh](https://iangoh.com/advisory). ## Related GrowthDex tactics - [Notion Any workspace scope before Marketplace push](/growth-ideas/notion-any-workspace-scope-before-marketplace-push/) - Marketplaces, Onboarding, Product Strategy - [Notion auth template choice before empty install](/growth-ideas/notion-auth-template-choice-before-empty-install/) - Onboarding, Activation, Product-led Growth - [Notion page picker full access before rollout video](/growth-ideas/notion-page-picker-full-access-before-rollout-video/) - Onboarding, Enterprise Rollout, Brand Trust - [Notion post-install database seeding before manual sharing](/growth-ideas/notion-post-install-database-seeding-before-manual-sharing/) - Activation, Onboarding, Retention - [Notion owned-domain link preview before generic embed](/growth-ideas/notion-owned-domain-link-preview-before-generic-embed/) - Product-led Growth, Brand Trust, Community-led Growth ## Essay chronology - [Newer essay: The plugin should prove the work before the marketplace scales it](/blog/the-plugin-should-prove-the-work-before-the-marketplace-scales-it/) - platform-led growth, marketplaces, developer tools - [Older essay: The social account should arrive with a map](/blog/the-social-account-should-arrive-with-a-map/) - social growth, community-led growth, brand trust ## Keep reading - [The Telegram Mini App should open where the habit already lives](/blog/the-telegram-mini-app-should-open-where-the-habit-already-lives/) - product-led growth, onboarding, brand trust - [The app directory page should answer the admin before the install](/blog/the-app-directory-page-should-answer-the-admin-before-the-install/) - marketplaces, brand trust, product-led growth - [The Stripe app page should finish the install thought](/blog/the-stripe-app-page-should-finish-the-install-thought/) - marketplaces, onboarding, brand trust ## Continue through the blog - [SaaS](/blog/#path-saas) - 3 essays in this path - [AI products](/blog/#path-ai-products) - 3 essays in this path ## Sources - [Notion Docs: List on the Marketplace](https://developers.notion.com/guides/get-started/marketplace-listing) · [GrowthDex source hub](/sources/notion-docs-list-on-the-marketplace-developers-notion-com/) - [Notion Docs: Public connections](https://developers.notion.com/guides/get-started/public-connections) · [GrowthDex source hub](/sources/notion-docs-public-connections-developers-notion-com/) - [Notion Docs: Authorization](https://developers.notion.com/guides/get-started/authorization) · [GrowthDex source hub](/sources/notion-docs-authorization-developers-notion-com/) - [Notion Docs: Preparing your connection for users](https://developers.notion.com/guides/get-started/preparing-for-users) · [GrowthDex source hub](/sources/notion-docs-preparing-your-connection-for-users-developers-notion-com/) - [Notion Docs: Introduction to Link Previews](https://developers.notion.com/guides/link-previews/introduction) · [GrowthDex source hub](/sources/notion-docs-introduction-to-link-previews-developers-notion-com/) ## Editing notes - Kept the piece on one plain claim: the connection should earn the first workspace, not just the OAuth click. - Used concrete mechanics like installation scope, template duplication, page-picker access, workspace-level database creation, and owned-domain unfurls instead of abstract ecosystem language. - Linked the new Notion tactics to existing marketplace, template, and discovery-surface pages so the essay reads like one operating system rather than five isolated tips. - Ended with a one-week operator test instead of a generic summary about collaboration platforms. ## Advisory If you want help turning this into a growth system, Ian Goh offers advisory at https://iangoh.com/advisory.