Skip to content

Auth and access

Auth and access explains how app users establish credentials, sign in, reset passwords, and lose access. Maker account passwords are separate from published-app user passwords.

Method User experience Best for
Email OTP User requests a temporary code each time Passwordless portals
Email & password User establishes an app-specific password Controlled users and repeat sign-in
Google / Auth0 / Okta External provider authenticates the user Existing organization identity

Configure the primary method under Users. Configure external-provider credentials under Integrations, then enable the provider and publish.

  1. Maker adds the named user from Users.
  2. NotionApps provisions the app-specific identity and sends an invitation.
  3. User opens the expiring, single-use link.
  4. User enters and confirms a password that meets the displayed policy.
  5. User returns to the published app and signs in.

End user:

  1. Select Forgot password on the app login.
  2. Enter the email.
  3. Open the reset email.
  4. Enter and confirm the new password.
  5. Return to the app.

Maker:

  1. Open Users and select an Active user.
  2. Choose Send password reset.
  3. The user completes the emailed flow. The maker never sees the password.

Disable blocks login and invalidates existing sessions. Re-enable restores access eligibility; it does not reveal the password. If the credential or active state changes through a Users-database sync, session invalidation also applies.

When Email & password signup is enabled, the new user verifies the email before the first password login completes. Use maker-controlled Add User instead when open enrollment is not intended.

Additional provider buttons appear to everyone on the login screen. Do not enable Google “only for staff” in a mixed audience app unless all visitors may use it. Use separate apps or another access design when provider visibility must differ.

  • Setup and reset links expire and are single-use.
  • Rate limits apply to sign-in, signup, setup, and reset paths.
  • Responses avoid exposing whether an arbitrary email exists.
  • App identities are isolated by app.
  • Duplicate provisioning retries are idempotent.
Symptom Action
Setup link invalid Resend invitation.
Reset link expired or used Send a new reset.
User has a Notion row but no password Send invitation from Users.
User can authenticate but sees no data Check Role, Active, visibility, and Data Restriction.
External provider button missing Configure integration, enable provider, publish.