You may want to capture information in your onboarding flow, whether it’s a customer’s email for communication purposes, alias, first name, or other fields.

We have a few fields pre-made for you. All the fields but 3 are are standard input fields, but these 3 have custom attributes:

  1. Email - this field has standard email validators and is unique for each project environment (Sandbox/Live).
  2. Phone - this field has standard phone validators, a country selector, and can be unique for each project environment (Sandbox/Live).
  3. Username this field is a string that is unique for each project, and has the following validations:
    1. Letters A-Z, a-z, numbers 0-9, or symbols $ ! # % ?
    2. Must be length 5 to 20
    3. Cannot contain consecutive symbols
  4. T-shirt size - this field is a dropdown with the standard options available (XS, S, M, L, XL, XXL).


We want to make this as simple for you. Go to the configurations page and click on the Customer Information Capture card.

Here you specify which fields you want to collect during onboarding. For each field, you can:

  1. Enable for sandbox/live
  2. Select whether this is optional or mandatory.

Simply save the settings and on the next log in, a user be prompted to enter the information in onboarding. For email or phone, select if you want to enable OTP verification or to enforce uniqueness. Note that if either are selected as log in methods, then OTP Verification and Uniqueness will be enabled by default.

But wait, what happens with your current users if you change the settings?

No big deal. If you make certain fields required, then the next time a user connects to your application, we’ll ask them to enter the field that you just made mandatory. That way, your users will stay up to date with the fields that you need.