🆕Sign up

Canonical Users page for self-serve signup: allowed domains, terms/privacy links, and default field values. Do not add a parallel “Identity 2” page.

What this is / when to use it

Signup lets a new person create an app-user row (and a login) without you adding them by hand. Use it for client portals and member apps. Turn it off for staff-only tools.

When not to: the app is public and has no users database. Public apps do not sign up.

Before you start

1. The app is private.

2. A Users database is linked.

3. Primary auth is Email OTP or Email & password. Additional Google / Auth0 / Okta can sit beside it. See Auth and access.

Build it

1. Open Users → Sign up.

2. Turn Allow sign up on.

3. Optionally set allowed email domains (for example example.com). Addresses outside the list are rejected.

4. Add terms and privacy URLs. The signup screen shows checkboxes / links.

5. Set default field values on the new user row (Role = Client, Active = true).

6. Confirm identity dual-write if you use role_field_id / active_field_id / profile_field_ids. See Identity admin.

7. Publish. Open the app in a private window. Sign up with a permitted email. Confirm the Users row.

Every control

Control	What it does
Allow sign up	Shows the signup entry on the login screen.
Allowed domains	Comma-separated hosts. Empty = any email.
Terms URL	Linked from signup.
Privacy URL	Linked from signup.
Default field values	Written on the new Users row (EXACT values).
Login methods	Primary + additional auth types. Not signup itself, but required for the new user to return.

What users see

Login screen → Create account → email/password or OTP → optional terms → they land on the default screen. If the domain is blocked, they see a rejection, not a blank app.

Limits and plans

• App users meter counts each successful signup. See Plans.

• Phone OTP (OTP_NUM / AuthType.PHONE) still exists in the product types for older apps. New apps should use Email OTP (OTP_EMAIL) or Email & password (EMAIL_PASS). Phone is not offered as a first-class new primary method in the current Users UI; if an existing app already uses it, it continues to work until you migrate.

• SSO (Auth0/Okta) signup still creates a Users row; defaults still apply.

Example

A client portal: signup on, domains empty (any client email), terms + privacy URLs, default Role = Client, Active = true. Staff are added by Add/Remove users, not signup.

Fix problems

Symptom	Likely cause	What to do
Signup missing	Off, or app public	Turn on. Make private.
Valid email rejected	Domain list typo	Fix allowed domains.
User row missing Role	Defaults not set	Set default field values.
Google signup but they want password	Separate troubleshooting page	Google vs email/password.

Related

Private apps. Identity admin. Auth and access.