Reuse Lovable workspace identity in your app

1. 1

   Confirm your Lovable workspace is on a Business or Enterprise plan and that your project uses TanStack Start.

   These are technical requirements for the feature to work. If your project is older, you might need to update it.

2. 2

   If you are a workspace admin, check that 'Lovable workspace identity' is allowed in your workspace's 'App login methods' settings (Settings → Security → Privacy & security).

   This is a one-time workspace-wide permission that allows apps to use this feature. It's usually allowed by default.

3. 3

   In your Lovable project chat, tell Lovable you want to use the signed-in Lovable user's identity for your app.

   This tells Lovable to automatically set up your app to recognize who is using it based on their Lovable login, instead of building a separate login system.

4. 4

   Test your app in preview while signed in to Lovable.

   This lets you confirm that the app correctly identifies you and displays your information, like your name or email, as intended.

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

Workspace identity reuse

This means your app can automatically tell who is using it by checking their existing Lovable login, so they don't have to log in again.

SSO (Single Sign-On)

A way for people to log in once to one system (like Lovable) and then automatically be logged into other connected systems (like your company's other tools) without typing their password again.

TanStack Start

A modern technical foundation that Lovable uses to build apps. Newer projects use it, and older ones might need an upgrade to use certain features.

Built-in backend (Cloud)

A part of Lovable that handles things behind the scenes, like storing data or running code, without you needing to set up your own servers. It's useful for apps that need to save information for each user.

• Assuming this feature works for public or customer-facing apps; it's only for your Lovable workspace members.
• Trying to use this feature on older Lovable projects that are not on TanStack Start.
• Not explicitly telling Lovable you want to use the 'signed-in Lovable user' for identity, which might lead to Lovable building a traditional login page instead.
• Mixing workspace identity reuse with a separate app login flow unless you specifically intend to create a complex, hybrid system.