QAlaunch

Base44 app forces visitors to log in: how to make pages public

Base44 sends every visitor to a login screen when App Visibility is set to Private or Workspace, or when the app is Public but every page was protected or the data on public pages needs sign-in. Set Dashboard > Overview > App Visibility to Public, ask the AI chat to protect only the pages that need an account, and make only genuinely public records readable without login.

Opens your site in a real browser on desktop and phone. Free, about two minutes, no signup. Full report from $19.

What you'll see

Someone clicks your link from an ad or social post and sees a sign-in form instead of your landing page. Search results and link previews show nothing useful. You do not notice, because you are always logged in when you check the app.

Why it happens

1. App Visibility is not Public

Private allows only invited people and Workspace allows only your Base44 workspace members; both require a login. Older apps may still show the deprecated Public (login required) option.

2. Every page is protected

In a Public app the AI chat can protect pages and redirect signed-out visitors to login. If it protected all of them, including the homepage, the effect is the same as a private app.

3. Public pages read private data

If a landing page shows records from an entity whose permissions require sign-in, signed-out visitors get an empty or broken page, and crawlers get only a general summary.

4. SSO enforcement on the workspace

When your workspace enforces SSO, Base44 does not offer Public (no login), so the app needs a login regardless of other settings.

How to fix it

  1. Open Dashboard > Overview and set the App Visibility dropdown to Public.
  2. Ask the AI chat which pages are protected, then have it protect only the ones that need an account, such as the dashboard and settings.
  3. Review data permissions for the entities your public pages display and make only safe, public records readable by anyone. Keep user data in protected entities.
  4. If the workspace enforces SSO and you need a public marketing page, check with your workspace admin.
  5. Open the app in a private window on your phone and click through every public page while signed out.
  6. Once the landing page is public, go to Dashboard > SEO & GEO and check that page's Search visibility is on, so the page you just opened up can actually be found.

Prompt to paste into Base44

Keep the app Public. Make the Home, Pricing and About pages viewable without logging in, and require login only for /dashboard and /settings. Make sure no user data appears on the public pages, and redirect signed-out visitors to login only when they open a protected page.

How to check it's fixed

  • Open the domain in a private window on a phone: the landing page should render with no login prompt.
  • Open /dashboard while signed out and confirm you are sent to login, so private pages stay private.

What a QAlaunch scan shows for this

  • A login screen where the homepage should be: the scan visits as an anonymous visitor and sees exactly what a new customer sees.
  • Links and the main call to action that redirect to a login page instead of content.
  • Missing title and description on the page crawlers receive.

See exactly what a full report contains in the sample report.

Frequently asked questions

Will making the app Public expose my users' data?

Not by itself. Visibility controls who can open the app; data permissions control who can read each entity. Keep sensitive entities restricted and protect the pages that show them.

What is Public (login required)?

An older option that Base44 now marks as deprecated. On current apps, choose Public and protect individual pages instead.

How does this affect Google?

Base44 keeps sign-in pages out of search automatically in a public app. If the whole app needs a login, crawlers see nothing to index, so public pages are a must for search.

How can I share a private app with a few people without making it public?

Leave it Private and use Send Invites or Copy Link on the Overview page. Uninvited visitors can request access after verifying their email, which suits a client preview or an internal tool better than opening it to everyone.

Done for you · not automated

Rather have a QA engineer test it by hand?

If this is a site you're launching or handing to a client, I'll go through it by hand, including the Base44-specific issues a scan can't reach, like logged-in flows.

$299one-time · 3 business days
  • Up to 10 key pages tested by hand, not a scan
  • Every flow a customer uses: forms, sign-up, checkout, booking
  • Real mobile and desktop browsers
  • A written report in plain language, with screenshots
  • A 15-minute call to walk you through it
  • 10 years of professional QA experience

Tell me about your site and I'll reply personally, usually the same day.

No payment now. I'll confirm scope and price first.

Related fixes

More for Base44: all Base44 fixes · Base44 testing · the Base44 pre-launch checklist

Written by Waqas Ahmad, QA engineer with 10 years of professional testing experience. Last checked October 26, 2026.

Sources: Base44 docs: managing access · Base44 docs: SEO and search visibility