Email and OAuth login for your SaaS
Start with email-code login, optional Google and GitHub sign-in, a compact account menu, and a separate administrator login.
On this page
Customers can create an account with an email code and return to their account center. Google and GitHub sign-in are available when you configure those providers.
How it works
Choose an available method
Open the account page. The interface shows the methods enabled by the backend.
Complete verification
Enter your email code or complete the configured provider flow. A new email account is created after verification.
Continue your task
Use the account menu to view the read-only sign-in email or sign out directly. Open the account center for subscriptions, credit history and referrals.
One identity across the customer journey
The customer account connects subscriptions, credit transactions, purchases, and referrals. It gives your product a place to continue after a visit to a public page.
Customer and administrator access have different jobs
Customers use their own account center and view a read-only sign-in email in the account menu. Authorized administrators use a separate console to operate the site; a normal customer login does not grant administrator access.
Limitations
- Email delivery and OAuth require your own service configuration. Available login methods depend on the providers enabled for this site.
- Team invitations, enterprise SSO, and your product's organization model still need their own implementation.
Questions
Do customers need a password?
The supplied customer flow uses email codes or an enabled OAuth provider. The administrator password flow is separate.
Does downloading the template enable Google login?
No. Register your own OAuth application, configure the backend credentials and callback, and enable the provider before offering it to customers.