🔐Private apps

A Private app requires sign-in before protected screens and personalized data are available.

When to use Private

• Client or employee portals

• Each user should only see their own rows (Data Restriction)

• Any app where the share link alone is not enough

Setup checklist

1. Open Users in the builder left rail.

2. Set the app to Private (Is the app public or private?).

3. Link or create a Users database (Create Users Database).

4. Map User Name and Email Address properties.

5. Choose Email Address + Login Code (the shipping Login Method). Optionally enable Allow Google login on a paid plan.

6. Add at least one test App User.

7. Configure Data Restriction on databases that must be personalized.

8. Publish, then open the live URL signed out — the login step should appear.

9. Complete a real OTP (or Google) login; also spot-check with View as.

Login methods (shipping vs not)

Available today	Not available / not ready
Email OTP (Email Address + Login Code)	Email + password (Coming soon in UI)
Google login (paid; Integrations)	Phone OTP in the current Login Method picker
	Enterprise SSO (Okta / Auth0)
	Microsoft login

Details: Auth and access.

Allow users to sign up

Private apps can enable Allow users to sign up and optionally restrict Allowed domains. Empty domains = any email domain. See Sign up.

Mixed public + private

Keep a public landing (often a Content Page) and require login for the rest:

• Build a mixed public–private portal

• Per-screen public access

Related

• App Users

• Google Login

• Video: Private apps