Back to rankings

Lovable: Workspace Identity Reuse for Internal Apps

LovableView original changelog

On Business and Enterprise plans, apps built for internal team use can now automatically recognize the signed-in Lovable user, with no separate login page and no second sign-in. The app can read the current user's name, email, and Lovable user ID directly, cutting the auth boilerplate needed for internal tools.

Key Takeaways

  • Internal apps built on Lovable can now auto-recognize the signed-in Lovable user with zero login UI.
  • Works regardless of how the user signed into Lovable (SSO, Google, or email), and does not require workspace SSO to be configured.
  • The app can read the user's name, email, and Lovable user ID directly, enough to power internal tools and admin dashboards.
  • Available on Business and Enterprise plans, currently scoped to newer projects on the TanStack Start stack.
  • The rollout is gradual, so it may not yet be visible in every eligible workspace.
  • Complements the same-window Custom Publish Audiences feature: one controls who can access an internal app, the other removes friction once they're in.

No More Second Login for Internal Apps

Apps built for a team can now automatically recognize the signed-in Lovable user, with no login page and no second sign-in. Whoever is already signed in to Lovable, whether through workspace SSO, Google, or email, is recognized by the app, so internal tools, admin dashboards, and workspace-only apps no longer need their own login flow.

How It Works

The app can read the current user's name, email, and Lovable user ID directly. This does not require workspace SSO to be configured, and is available on Business and Enterprise plans, currently for newer projects on the TanStack Start stack. Lovable notes the rollout is gradual, so it may not appear in every workspace yet. Workspace admins and owners control it from Workspace settings, Privacy & security, App login methods.

Why It Matters

Internal tools are one of the most common things teams build in Lovable, and until now each one needed its own authentication flow even though the person opening it was already signed in to the workspace. Removing that duplicate step cuts friction for end users and reduces the auth boilerplate builders need to add themselves.