Managing login and registration

Choose how people sign up and access your app with authentication.

Authentication controls how your app’s users sign in, register, and access its features. With Base44, you can choose among popular login providers, decide how data is collected at registration, and shape the experience for your users.

---

Choosing login options for your app

Choose the authentication methods that work best for your app and your audience. You can offer multiple ways for people to sign up, such as email, Google, or other providers, so that login stays simple, secure, and familiar.

You can enable more than one login option.

To choose your app’s login options:

1. Click Dashboard in your app editor.
2. Click Settings.
3. Click Authentication.
4. Enable the toggle next to the relevant authentication options:
   • Email and password: Allow people to create an account with their email address and a secure password.
   • Google: Allow people to log in using their Google account credentials.
   • Microsoft: Allow people to log in using their Microsoft credentials.
   • Facebook: Allow people to log in using their Facebook credentials.
   • Apple: Allow people to log in using their Apple account.
   • Single sign-on (SSO): Connect an external identity provider that supports OIDC, such as Okta or your company’s identity provider, so people can log in using credentials from that provider.
     Important: SSO is only available for the Elite plan. Learn more about setting up SSO.

Note: For Facebook login to work, the person logging in needs a verified Facebook account. If their Facebook email or identity is not verified, Facebook can block the login and show an error message. They must complete Facebook’s identity confirmation process in their Meta account before they can sign in to your app with Facebook.

---

Customizing the Google login

Base44 gives you 2 ways to set up Google login, so you can manage how your users experience sign-in and how your brand is displayed:

• Default Google login: Fast setup using Base44’s credentials. The login window shows “Sign in with Google” and is branded with base44.com. To use this method, enable the Google authentication toggle and select Use the default Base44 OAuth.

• Custom Google OAuth: Connect your own Google Cloud client ID and secret in the Authentication panel. Your users will see your app’s domain, not “base44.com” when they sign in with Google. Custom Google OAuth is a great choice if you want full control over your login branding or need your app’s domain and messaging to appear in the Google login window. This is ideal for businesses that require a fully branded experience or need to meet enterprise requirements.

Before you begin:

• You must be on a Builder plan or higher to use custom Google OAuth.
• To set up custom Google OAuth, you must have a payment method connected to your project in your Google Cloud Console.

To set up custom Google OAuth:

1. Connect a custom domain to your app.
2. Go to Google Cloud Console and create a new project for your app.
3. Verify your domain here.
4. Set up your OAuth app by completing the following information:
   1. Overview: Enter your app information.
   2. Branding: Set up your app’s branding (learn more about branding):
      1. Add your logo. This must be similar to your app’s logo.
      2. Create a home page in your app following these guidelines.
      3. Create a privacy policy linked from your home page following these guidelines.
      4. Add a support page to your app.
      5. Add your domain as an authorized domain.
   3. Audience: Choose if your app is for internal or external use.
   4. Clients: Get your Client ID and Secret:
      1. Click Create client.
      2. Enter the relevant details including the following:
      • Authorized JavaScript origins: Enter your app domain.
      • Authorized redirect URIs: Enter https://app.base44.com/api/apps/auth/callback
      3. Click Create.
   5. Data Access: Select the following scopes:
      • openid
      • https://www.googleapis.com/auth/userinfo.email
      You must add a landing page to your app that includes your privacy policy and terms of service. These pages must be public and not behind a login. This is required for Google OAuth approval and lets your users see your legal information before signing in.

5. Go back to Base44 and finish setting up your custom login:
   1. Click Dashboard in your app editor.
   2. Click Settings.
   3. Click Authentication.
   4. Enable the Google authentication toggle.
   5. Select Use a custom OAuth from Google Console.
   6. Enter the relevant information from your Google OAuth app and click Update.
   Once you have completed the steps above, you need to wait for Google to verify and approve which can take up to 5 days.

---

Collecting data at sign-up

Personalize your app experience by collecting key details from your users when they sign up. You can prompt the chat to generate a custom sign-up form that gathers information beyond just an email and password (e.g. full name, company, or role) so you can onboard people smoothly and tailor their app experience from the start.

Choose where to store the data:

• Users dataset: Store data securely, viewable only by app admins. This is ideal for sensitive or admin-only details.
• Connected dataset: Store user responses in a separate public-facing dataset. This is recommended for data displayed or shared in-app (like company names).

---

FAQs

Click a question below to learn more about authentication.

Why didn't my user receive a verification or password reset email?

If people do not receive verification or password reset emails, start with these checks:

• Ask them to check their spam or junk folders in case the email was filtered.
• Let them know it can take a few minutes for some email providers to deliver the message.
• Ask them to add [e-mail] to their safe senders or allowlist so future emails are not blocked.
• During sign up, encourage them to enter their email address in lowercase and to check for typos.

If they still do not receive the email, ask them to click the resend link from your app.

If that does not work, remove their record from the Users list in your dashboard and ask them to sign up again with the same email address.

If several people report the same issue at the same time, or if resend and re-signup do not solve it, contact Base44 support with your app URL and the affected email addresses so we can check for any deliverability or platform issues.

Why do people see an error when they try to log in with Facebook?

This usually happens when the person’s Facebook account is not fully verified. Facebook can block the login until they confirm their identity and verify the email on their account.

Ask them to:

1. Open Facebook and go to Settings and privacy.
2. Go to Accounts Center.
3. Go to Verification and then Identity confirmation.
4. Complete the identity confirmation steps.

After they finish Facebook’s verification flow, they can try logging in to your app again with Facebook. Facebook controls this requirement, not Base44, so you cannot bypass it from your app settings.

How do I show a public landing page but require login for other pages?

It’s not possible to make some pages in your app public and keep others private. We know this is a common request, and we’re actively working on adding it. You can follow progress (and add your voice) here: Hybrid Apps – Authentication Support .

As a workaround, to set up your Base44 app so that everyone can visit your landing page while requiring users to log in for other pages, follow these steps:

1. Set your app to Public (no login required):
   In your Dashboard, go to Settings → App Settings. Set App Visibility to Public (no login required). This allows anyone to see your landing page.
2. Create your landing page with login and sign-up buttons:
   Prompt the AI to “create a landing page with login and sign-up buttons.” Make sure this is your app’s main page by selecting it under “Main Page” in your settings.
3. Require login for other pages:
   Ask the AI to require login on all other pages and redirect visitors who aren’t logged in back to your landing page.

With this setup, all visitors see your landing page first. Only users who have logged in or signed up can view the rest of your app’s pages.

How are passwords managed and what happens if someone forgets theirs?

Base44 automatically handles all passwords securely behind the scenes. If someone forgets their password, they can reset it directly from the login screen by clicking Forgot password?.

Can I add a logout option for my users?

Yes. Adding a logout option keeps things secure and gives users peace of mind. You can prompt the chat to include a Logout button and place it in the sidebar or app header, wherever it best fits your design.

Can I create a custom authentication flow from scratch in Base44?

No, Base44 does not currently support creating a fully custom authentication flow from scratch. This means you cannot build your own authentication pages, change the design or language of the built-in auth screens, or fully white label the authentication process. Authentication is managed by the platform to keep your app secure and consistent.

Features like white labeling are planned for the future, but are not available yet. Check out the feature request for more information.

Does Base44 support external authentication providers like Kakao?

Yes. Base44 supports external authentication providers that use OpenID Connect (OIDC), including providers such as Kakao.

If you are on the Elite plan, you can connect external providers such as Google, Microsoft, GitHub, Okta, or Kakao using Single sign-on (SSO) and the Advanced / Manual configuration option. You need your own account with the identity provider, and you are responsible for creating and managing the app, client ID, client secret, redirect URI, and any other credentials in that provider.

For step-by-step instructions, see the guide on setting up SSO in Base44.

Can I customize the login screen?

Currently, you cannot customize the design and styling of your login page.

Why am I getting an error when I use User.login() in the Base44 SDK? What should I use instead?

The Base44 SDK does not support User.login(), so if you try to use it in your code, you will see an error.

To log users in, always use base44.auth.redirectToLogin(nextUrl). This method sends the user to the login page and brings them back to your site after they sign in.

If you are having issues with authentication, check that you are using this correct method in your app.

Incorrect (will cause an error):

User.login(nextUrl);

Correct:

base44.auth.redirectToLogin(nextUrl);

Tip: If you see an error like “TypeError: User.login is not a function”, check your imports and ensure you are using base44.auth.redirectToLogin instead.

Can I preview the signup form on my app?

No. You cannot use or test your app’s signup, login, or logout flows inside the app preview window. Authentication features are only fully available on the live app.

To test your signup and login flows:

1. Publish your app.
2. Open your app’s live URL in a browser.
3. Go to the signup or login page.
4. Complete the flow with a relevant, valid email address.

This way you see the same experience that people will have when they sign up or log in to your app on the live site.

Why are users getting an 'invalid login' error?

The most common cause is that your app is set to Private. On a private app, only users who have been explicitly invited by email can log in. Anyone else will see an invalid login error, even if they enter valid credentials.

To check and update your app’s visibility:

1. Click Dashboard in your app editor.
2. Click Overview.
3. Under App Visibility, check the current setting.
   • If it is set to Private, make sure the user has been invited. Go to Users and click Invite User to add them.
   • If you want anyone to be able to sign up and log in, change the visibility to Public (Login Required).

Other possible causes:

• The user entered an incorrect email or password.
• The user has not verified their email address after signing up.
• The login session has expired. Ask the user to try logging in again.