Lovable: App User Connectors for Multi-Tenant Apps
LovableLovable introduced App User Connectors, letting each individual user of a published Lovable app connect their own third-party account (Google, Microsoft, Slack, Salesforce, HubSpot, Linear, Databricks, or Snowflake) instead of sharing one workspace-level connection. This unlocks true multi-tenant patterns where an app can act on behalf of each signed-in visitor, using that person's own permissions and data. Builders configure the OAuth client once; end users complete their own sign-in the first time they need the integration.
Sources & Mentions
1 external resource covering this update
A New Way to Connect Third-Party Accounts
Lovable expanded its connector system with App User Connectors, a new integration model built specifically for apps that serve many independent end users rather than a single team. Previously, Lovable's connectors were workspace-scoped: one shared account handled every request from every visitor to a published app. That model works well for internal tools, but it breaks down for consumer or B2B products where each user needs to see their own inbox, calendar, or CRM records rather than a shared company account.
How It Works
With App User Connectors, the builder configures the integration once at the workspace level by registering an OAuth application with the provider and setting up a client inside Lovable. From that point on, each individual end user of the published app goes through their own standard OAuth consent flow the first time they need the integration. Lovable exchanges that authorization for tokens, encrypts them, and stores them in its connector gateway, linked specifically to that user. The app then acts on behalf of each person using their own permissions and their own data, rather than a shared credential.
Supported Providers and Use Cases
At launch, App User Connectors support Google, Microsoft, Slack, Salesforce, HubSpot, Linear, Databricks, and Snowflake. This makes the feature especially relevant for multi-tenant SaaS products, internal tools distributed across an organization, or any published app where the value comes from personalized access to a user's own data, such as a scheduling app reading each user's individual calendar or a support tool pulling each rep's own CRM records.
Why It Matters
This feature addresses a structural gap that previously pushed builders toward third-party workarounds (such as Clerk- or WorkOS-based patterns) to achieve proper multi-tenant authentication in Lovable-built apps. By making per-user OAuth a native, first-class connector type, Lovable makes it meaningfully easier to ship apps intended for many independent users without having to hand-roll the underlying authentication plumbing.