The password field is not required. When the login feature is enabled, you can turn on the OTP (one-time password) option in the login field settings. When it's enabled, the user will receive a verification code to log in. The generated code will be valid for 15 minutes.
Important: Once a user has logged in, their login will be stored in their browser, so they will not have to log in every time they access an extension.
When using this feature, ensure that your field contains exactly one valid email address for each record and nothing else (e.g. do not use fields that contain multiple email addresses), as email verification will fail otherwise.
To set this up, go to:
Your Form/Portal settings
Share (for Forms) or Users Table & Login (for Portals) section
Locate the Login Fields setting
Click on a login field (see field type limitations below)
Turn on Require email verification to login or Require phone number verification to login.
Verification is only available for the following field types:
Single Text
Long Text
Email
Barcode
Single select
Multi select
Formula
Lookup
Phone
When using email verification it is usually recommended to only use the field containing the email address as your login field, since the email verification provides the authentication. When not using email verification, it is recommended to use at least two fields (e.g. username and password) for authentication. You should avoid maintaining sensitive credentials in your Airtable base. If email verification is not an option for you, we recommend that you use a pin field for login, instead of a password. Or in some cases, the login fields could be a combination of personally identifiable info. E.g. name, birthdate, phone number, address, etc. This way you will ensure that you don't have to store their password.
Email verification customization
Once you turn on this feature, two more fields will show up where you can set the custom sender name and the subject of the login verification email:
Custom subject for confirmation email (optional)
Custom sender name for confirmation email (optional)
You will also be able to set a Fallback phone number field so that users can enter their phone number instead to receive the OTP via SMS (restrictions based on geographical location may apply). The phone number entered by the user must match the phone number stored in the selected field for the record related to the email address entered prior. Otherwise you will see the following error:
Phone number doesn't match with existing records.