How do I add login to Lovable?

Ask Lovable to add authentication — it enables Lovable Cloud (if not already on), then generates sign-up/login pages and wires them to email, Google, or other providers.

How do I add user registration?

Ask Lovable to add sign-up with the fields and verification behaviour you want — it builds the form, creates the user in Lovable Cloud's auth system, and can store extra profile details in your database.

How do I add Google login?

Ask Lovable to add Google sign-in — it can use Lovable's managed Google OAuth for a quick setup, or your own Google Cloud OAuth credentials if you need custom branding or scopes.

How do I add password reset?

Ask Lovable to add a "forgot password" flow — it uses Lovable Cloud's authentication to email a reset link and lets the user set a new password.

Why isn't my login working?

Check the browser console for the actual error first — common causes are unconfirmed email, a redirect URL mismatch, RLS blocking the post-login profile read, or a provider (like Google) misconfigured for the current domain.

Why does my app keep redirecting to login?

This is almost always a session or route-guard bug: either the auth session isn't persisting, or a protected route checks auth state before it's loaded, so it bounces back to login even when signed in.

Why are verification emails not arriving?

Usually the email lands in spam, the sending rate limit on Lovable Cloud's default mailer has been hit, or you haven't connected a proper email provider yet.

How do I restrict pages to logged-in users?

Wrap the routes in a protected-route component that checks the current auth session and redirects signed-out users to login, and back this up with row-level security on any data those pages fetch.

How do I create admin users?

Add a `user_roles` table with an `admin` role, assign it to the specific user's ID, and check that role server-side (in RLS policies and any admin-only functions) rather than trusting a front-end flag.

How do I create different user roles?

Store roles in a dedicated `user_roles` table (never a column on the user's profile), and use a security-definer function to check roles inside RLS policies and route guards.

How do I build an admin dashboard?

Ask Lovable to build a role-gated route that lists and manages your data (users, orders, content), backed by RLS policies that only let accounts with the `admin` role query the underlying tables.

How do I delete a user?

Ask Lovable to add an admin action that deletes both the user's auth account and their related data (profile rows, uploads, etc.), since removing one without the other leaves orphaned records or broken references.

How do I let users edit their profiles?

Add a profile form bound to a `profiles` table row keyed by the user's ID, with an RLS policy that only lets each user update their own row, not anyone else's.

How do I test authentication properly?

Test with real, separate accounts in a private browser window for each role (signed-out, normal user, admin), checking both the UI and that the underlying API/RLS actually blocks what it should — not just what the interface shows.

How do I prevent normal users accessing admin pages?

Last checked 31 Aug 2026

Short answer

Guard the admin route with a check against the user's role from your `user_roles` table (not a front-end-only flag), and mirror that same check in RLS policies on any data the admin page loads.

Two places to enforce it

Blocking the page in the UI is necessary but not sufficient — the real barrier is the database.

Route guard: the admin route checks has_role(auth.uid(), 'admin') (via your roles function) before rendering, redirecting anyone else to a normal page or a "not authorised" screen.
RLS policies: the tables the admin page reads or writes must independently check the same role, so a non-admin can't just call the API directly and get the data.

How to set it up

Make sure only users with the admin role can view /admin and can query the admin-only tables. Redirect everyone else to the home page.

Confirm user_roles and a has_role() function already exist (see how-do-i-create-different-user-roles).
Ask Lovable to add the route guard using that function.
Ask Lovable to review RLS policies on every table the admin page touches, confirming they also require the admin role.

What usually goes wrong

Hiding an "Admin" nav link but leaving the route itself reachable by typing the URL directly.
Checking role once on page load and caching it in local state, so a role change doesn't take effect until next login — usually fine, but worth knowing.
RLS policies referencing profiles.role instead of user_roles, which reopens the self-promotion risk described in how-do-i-create-admin-users.

Testing

Create a second, non-admin test account and confirm it's actually blocked from both the page and the underlying API calls, not just the nav link.

Sources

Was this answer helpful?