> ## Documentation Index
> Fetch the complete documentation index at: https://lovable.generaltranslation.app/llms.txt
> Use this file to discover all available pages before exploring further.
# Clerk integration
> Learn how to integrate Clerk with your Lovable application
## Why Clerk?
[Clerk](https://clerk.com) handles authentication and user management so you don’t have to build it from scratch. With just a few prompts and config steps, you get:
* Secure sign-in & sign-up (social, password, MFA)
* Prebuilt UI components: user profiles, org management, impersonation
* Support for B2B apps (teams, roles, invitations)
* Integration with Supabase, Stripe (coming soon), and more
* Waitlist mode to manage early access
* Generous free tier: 10K MAUs
## Step-by-step integration guide
Here is a step-by-step guide:
Create a Clerk Account → [Clerk.com](https://clerk.com)
In the Clerk dashboard, create a new app
Sign in to Clerk & create a new app
Enable desired authentication providers (e.g. Google, GitHub)
Enable “Waitlist” under **Configure > Restrictions**
Copy your **Public API Key**
**Add Clerk to Your Lovable App**
In **Lovable**, add Clerk as your authentication provider.
Prompt Lovable:
Let's build a beautiful project and task management app in the style of Asana. Users should be able to login and signup using Clerk for authentication and user management. Let's start by building a great looking homepage and use Clerk's waitlist component to let users join while we build the rest of the app.
Paste your **Public API Key** when asked
Lovable scaffolds the login and sign-up pages
Deploy & test — you’re now using Clerk Auth
**Why use a waitlist?** – Gather early users before launching your app!
Use Clerk’s built-in waitlist to collect users pre-launch.
In Clerk dashboard: **Configure > Restrictions > Waitlist**
New sign-ups will show as **pending**
* Users who sign up will now be **pending approval**
* Admins can approve users from the Clerk dashboard
Customize waitlist emails (branding, content)
Set up team-based access in your app.
In Clerk dashboard: enable **Organizations**
Define roles (Admin, Member, Viewer, etc.)
Invite users to your org by email
Assign roles and permissions via dashboard
Prompt Lovable to:
Ask users to create/join an organization after sign-up
**Using Clerk’s User Profile Component**
* Provides a prebuilt user management dashboard
* Supports social logins & password authentication
* Users can manage their own accounts & 2FA
**What is Impersonation Mode?**
Admins can log in as any user to troubleshoot issues
Troubleshoot your app as if you were a specific user.
In Clerk dashboard > Users, click on a user
Click **Impersonate**
View your app from their perspective
Security: impersonators can’t perform sensitive actions (e.g. change password)
Combine Clerk Auth with Supabase backend.
**Why integrate with Supabase?**
* Store user data in a database
* Secure authentication with JWT tokens
* Connect authentication to app features
**How to integrate:**
In Supabase, go to **Settings > API > JWT Secret (**[**documentation**](https://clerk.com/docs/integrations/databases/supabase)**)**
In Clerk: **JWT Templates > Add Supabase**, paste JWT secret
Enable **Clerk as an authentication provider**
Update RLS policies to use `auth.uid()` from Clerk
Prompt Lovable to:
Let's setup supabase to integrate with Clerk. Clerk has been configured with a Supabase secret. Here's an example of implementing the supabase client using Clerk. Use this as a reference.
*\[Supabase client configuration import]*
Confirm Clerk-issued tokens are accepted by Supabase
**Why use a custom domain?**
Boosts brand recognition & trust
[More information here](https://docs.lovable.dev/tips-tricks/custom-domain).
In Lovable: **Project > Settings > Custom Domain**
Enter your purchased domain (e.g. `app.yourcompany.com`)
Lovable auto-configures DNS (no need to leave Lovable)
Deploy & test your app with the new domain.
Done ✅ — your app is now white-labeled
**Your app now has:**
* Secure authentication with Clerk
* A waitlist to collect early users
* User & team management features
* Supabase database integration
* A professional custom domain
## Bonus: Build B2B features in minutes
Clerk supports:
* Role-based access for organizations
* Invite flows (email-based, pre-built UI)
* Organization profile customization (logo, name)
* Multi-org switching (e.g. Slack-style)
**Ask Lovable to:**
Add organization switcher UI
Let users invite teammates
## Tips & troubleshooting
* **Already using Supabase Auth?** You can switch to Clerk without rewriting your app logic. Just configure JWT correctly and swap auth provider.
* **Email customization:** Clerk lets you edit all transactional email templates (waitlist, invitations, approvals).
* **Mobile login**: Clerk supports passkeys, OTP, and SMS — no extra config needed in Dev Mode.
* **Compliance**: Clerk is SOC2, HIPAA, and GDPR compliant.
## Frequently Asked Questions (FAQ)
Yes. Clerk and Supabase work well together. You just need to:
* Set up Clerk to issue JWTs
* Add Supabase’s JWT secret in Clerk
* Update Supabase RLS policies to use Clerk’s `auth.uid()`
This lets you plug Clerk into an existing Supabase-backed app with minimal changes.
Only for production. In development mode, Clerk provides shared credentials for testing. For production:
* Set up your own Google/GitHub/etc. credentials
* Add them in Clerk under **OAuth settings**
* **Users**: Individuals who can log in to your app
* **Organizations**: Groups of users (teams, companies)
Use organizations when you want:
* Role-based access (Admin, Member, etc.)
* Users to invite teammates
* B2B SaaS-style flows
It allows admins to log in as any user — super helpful for:
* Debugging user issues
* Understanding their experience
* Providing live support
Clerk limits what impersonators can do (e.g., no password changes).
Yes. Clerk offers:
* Full CSS support via `appearance` props
* The option to build fully custom UIs using Clerk React hooks
You can keep the out-of-the-box look or fully match your app’s brand.
Currently:
* Users are auto-notified when approved from the waitlist
* Bulk email support is **coming soon**
For now, export emails and use your preferred email tool.
Yes! Clerk has a generous free tier:
* Up to **10,000 Monthly Active Users (MAUs)**
* Paid plans start at **\$25/month**, with usage-based pricing after
You can use it in production without paying until you scale.
Yes. Clerk is:
* **SOC 2 certified**
* **HIPAA-compliant**
* **GDPR-ready**
Ideal for teams building in regulated industries.
Coming soon. You’ll soon be able to:
* Define plans (e.g. Free, Pro, Enterprise)
* Let users/orgs manage subscriptions from Clerk’s UI
* Automatically sync data to Stripe
Follow [@clerkdev](https://x.com/clerkdev?lang=en) on X for updates.
Want a question added to this FAQ? [Let us know on Discord](https://discord.gg/lovable-dev)!
## Final thoughts
Clerk turns authentication into a prompt. You don’t need to build it yourself.
**With just a few clicks and prompts, your app now has:**
* Secure, scalable authentication
* Team & organization management
* Impersonation tools for debugging
* Supabase-backed data and access control
* Custom domain support for a polished UX
[Clerk](https://clerk.com) handles authentication and user management so you don’t have to build it from scratch. With just a few prompts and config steps, you get:
* Secure sign-in & sign-up (social, password, MFA)
* Prebuilt UI components: user profiles, org management, impersonation
* Support for B2B apps (teams, roles, invitations)
* Integration with Supabase, Stripe (coming soon), and more
* Waitlist mode to manage early access
* Generous free tier: 10K MAUs
## Step-by-step integration guide
Here is a step-by-step guide: