Sign up

Signup allows a visitor to create their own app-user row and login. It is intentionally different from maker-controlled Add User. Turn signup on only when self-enrollment is part of the app’s design. For staff-only tools and invitation-only portals, leave signup off and add named users from Builder.

Before you start

1. Make the app Private.
2. Link a Users database.
3. Select Email OTP or Email & password as the primary login method.
4. Map Name and Email.
5. Decide the default Role, Active value, and any profile defaults.

Configure signup

1. Open Users → Sign up.
2. Turn Allow users to sign up on.
3. Optionally list allowed email domains. Leave the list empty only when any valid email may register.
4. Add Terms and Privacy URLs when required.
5. Configure Default user fields, such as Role = Client and Active = on.
6. Confirm that defaults do not grant staff or administrator access.
7. Publish.
8. Test in a private browser using a non-maker address.

Email-and-password verification

New public password signups must verify the email address before the first password login completes. The person receives a verification message and follows its link before entering the app. This prevents an unverified address from becoming an active password user.

Expected flow:

1. Visitor selects Create account.
2. Visitor submits name, email, and password and accepts any required terms.
3. NotionApps validates the domain and plan/user limit before writing the new account.
4. A verification email is sent.
5. The visitor opens the verification link.
6. The visitor returns to the app and signs in.

Do not tell users they are immediately signed in after password signup. Verification is required.

Default fields

Signup collects only the public signup inputs. If navigation or visibility depends on Role, Active, Company type, or another Users property, set safe defaults before enabling signup. Defaults also apply to Builder Add User where compatible. Relation fields generally require a separate onboarding step.

Controlled access alternative

If the maker must approve every person:

1. Turn Allow users to sign up off.
2. Publish.
3. Use Users → Add User for each authorized email.
4. Send the setup invitation and monitor Access.

Turning signup off does not disable users who are already Active.

Limits and safeguards

• The app-user meter is checked before signup data is written.
• Allowed domains compare the email domain, not free-form text in another field.
• Rate limits protect repeated signup and verification attempts.
• Error responses do not reveal whether an email already belongs to an account.
• SSO signup still creates a Users row and applies compatible defaults.

Troubleshooting

Symptom	Check
Create account is missing	App must be Private, signup on, and changes published.
Valid email is rejected	Check allowed-domain spelling.
User receives no verification email	Confirm address, spam folder, and retry after the rate-limit window.
User verifies but sees no screens	Check Role, Active, defaults, and visibility rules.
Signup says the limit was reached	Free capacity or change plan; no partial row should be created.

Related

• Private apps
• Add/Remove users
• Email & password