KBAISE/ for lovable
Library
Docs

Reuse Lovable workspace identity in your app

about 10 minBuildingchecked 4d agoOfficial page
The short version

You can make apps you build in Lovable automatically recognize your teammates who are already logged into Lovable, so they don't have to log in again. This lets your app know their name, email, and Lovable user ID without a separate login screen.

Anyone building an internal app for their team needs this when they want the app to know who is using it without extra login steps.

Do this, in order

  1. 1

    Confirm your Lovable workspace is on a Business or Enterprise plan.

    This feature is only available on these plans.

  2. 2

    Confirm your project uses TanStack Start. If you're unsure, ask Lovable: 'What stack is this project on?'

    This feature requires projects built with TanStack Start. Older projects might need to be upgraded.

  3. 3

    Check that 'Lovable workspace identity' is 'Allowed' in your workspace's 'App login methods' policy. (Workspace settings → Security → Privacy & security → Configure under App login methods)

    This is a workspace-level setting that must be enabled for any app to use the feature. It's allowed by default.

  4. 4

    In your project chat, ask Lovable to use the logged-in user's identity. Be specific about what you want the app to do with this information.

    Lovable will modify your app's code to recognize the logged-in user and use their details as you described.

  5. 5

    Test your app in preview while logged into Lovable to ensure it recognizes you and displays your information correctly.

    This verifies that the identity reuse is working as expected before sharing or publishing the app.

  6. 6

    To test the logged-out experience, open the published app in a private browser window.

    This helps you see what anonymous visitors or those not logged into Lovable will experience.

Paste this into your project

Use Lovable workspace identity for this internal app. Show the logged-in user's name and email in the header. If no user is available, show a logged-out state. Do not add a separate email or Google login flow.

Words decoded

Workspace identity reuse
This means your app can automatically tell who is using it by checking if they are already logged into Lovable, without asking them to log in again.
TanStack Start
This is a modern way Lovable builds apps, which is required for this feature to work.
Workspace SSO
This is how your team logs into Lovable itself using your company's existing login system, like Google or Okta.
SAML SSO for apps
This is a way for outside users of your app to log in using their own company's login system, not related to Lovable accounts.
Built-in backend (Cloud)
This refers to Lovable's own database and server services that your app can use to store and manage data.

Where people get stuck

  • Trying to use this feature on a Free or Team plan, as it's only available on Business and Enterprise plans.
  • Using an older project that doesn't run on TanStack Start, which is a requirement for this feature.
  • Expecting public or customer-facing apps to use this, as it's designed for internal team members already in your Lovable workspace.
  • Not being specific in your prompt to Lovable, which might lead to a traditional login flow being built instead of using Lovable workspace identity.
  • Forgetting to set up two-factor authentication if your workspace requires it, as users without 2FA won't be recognized by the app.
  • Mixing Lovable workspace identity with a separate app sign-in flow unless you specifically intend to build a complex hybrid system.

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.