Lovable: Notion App User Connector
Lovable extended its App User Connectors to Notion, letting each individual person using a published Lovable app connect their own personal Notion workspace instead of the app relying on one shared account. Builders configure OAuth once; every end user authorizes their own connection at runtime. This targets multi-tenant apps such as internal tools, client portals, and knowledge-base products where different users each need their own Notion data.
Featured Video
A video we selected to help illustrate this changelog
Key Takeaways
- Per-user authentication replaces the single shared account model. Each person using a published Lovable app now connects their own Notion workspace independently.
- Builders set up OAuth once, and every end user authorizes separately at runtime, keeping each visitor's Notion data isolated.
- Multi-tenant apps benefit most. Support dashboards, client portals, and knowledge-base tools can now pull from each user's own Notion source of truth.
- Notion had previously been more of a build-time, single-workspace integration in Lovable; this update extends it to true runtime, multi-user access.
- The change fits Lovable's broader pattern of expanding its App User Connectors category alongside other integrations shipped the same week.
- No custom OAuth plumbing is required from builders to support per-user Notion access.
Sources & Mentions
2 external resources covering this update
Notion Joins App User Connectors
Lovable added Notion to its App User Connectors, the connector category built specifically for apps with multiple end users. A standard connector authenticates once with the builder's own account; an app user connector instead lets each person who uses the published app connect their own third-party account independently.
What Changed
Every person who uses your published app can now connect their own Notion workspace directly from inside the app, rather than the app sharing a single Notion account across every user. The builder still configures OAuth once at the app level; each individual end user then authorizes their own Notion account separately, so one visitor's connected pages and databases stay scoped to that visitor and are never exposed to another.
Why It Matters
This suits multi-tenant apps where different users need to read or write their own Notion content: think a support dashboard where each rep pulls from their own knowledge base, a client portal where each customer connects their own docs, or a personal productivity tool built on Lovable. Before this update, builders either hard-coded a single shared Notion connection or worked around the limitation entirely. Notion joins a growing family of app user connectors Lovable has been rolling out, reinforcing its push toward apps that behave like real multi-user products rather than single-workspace prototypes.