App user connectors: let your users connect their own accounts
App user connectors let each person using your published app link their personal third-party account, like their own Gmail or Salesforce. Your app then displays and manages only their data rather than using one shared company account.
You need this when building apps where visitors must view or edit their own external data, such as their personal inbox, calendar, or CRM records.
Do this, in order
- 1
Create an OAuth application in the third-party provider's developer portal (such as Google Cloud, Microsoft Entra, or Salesforce) and add Lovable's redirect URL: https://connector-gateway.lovable.dev/api/v1/app-users/oauth2/callback.
The provider needs to recognize Lovable's secure gateway as an authorized destination when your users sign in.
- 2
Go to the Connectors section in your Lovable dashboard, select your provider, click add client, and paste your provider Client ID and Secret.
This stores the connection configuration once for your workspace without storing any individual user data.
- 3
Enable Offline access in the client's advanced settings if you are using built-in authentication or publishing a public app.
Offline access gives your app a persistent connection key so it can fetch data for that user when they are signed in or during background syncs.
- 4
Link the client to your current Lovable project.
Your project needs permission to use this client configuration before Lovable can build the integration.
- 5
Ensure your app has user sign-in enabled, such as Lovable built-in authentication.
The app user connector must identify who is currently logged in so it can attach their specific third-party credentials to their profile.
- 6
Ask Lovable in the project chat to add the connect button and build the user-specific feature.
Lovable will generate the login flow and gateway calls to fetch that specific user's records.
Paste this into your project
Add a user authentication flow if not already present. Then add a 'Connect Google Calendar' button on the dashboard that lets the currently signed-in user authorize their own Google account through the app user connector. Once connected, display their upcoming calendar events in a clean list, and provide a disconnect button to let them revoke access.
Words decoded
- App user connector
- An integration setup where every visitor connects their own personal account, rather than everyone sharing one admin account.
- OAuth consent screen
- The popup window from a service like Google or Slack asking you to approve an app accessing your data.
- Connector gateway
- Lovable's secure middleman server that holds credentials and handles token refreshes so sensitive keys never enter your app code.
- Offline access
- A setting that gives your app permission to fetch data for a user even if they are not actively logged into Lovable workspace identity.
Where people get stuck
- Do not try to verify the lovable.dev domain in your provider's console; you do not own it, and domain verification is not required just to register the callback URL.
- Do not attempt to use app user connectors without authentication in your app, because Lovable must know which visitor owns the connected account.
- Do not forget to provide a disconnect button in your app UI so users can revoke their tokens whenever they want.
- If you change or disable Offline access on Business or Enterprise plans, you must unlink the client from all projects first, which temporarily stops user requests.
The short version, steps, decoder and prompt on this page are written automatically from Lovable's own documentation and can lag or misread it. The official page is always the authority.