> For the complete documentation index, see [llms.txt](https://docs.cubu.com/guides/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cubu.com/guides/understanding-the-basics/portals/prerequisites-and-data-collection.md). # Prerequisites & Data Collection ## The Prerequisites Flow Depending on the selected service's Prerequisite configuration, the portal may ask the customer for a phone number, email, or customer ID.

The Portal's Service Settings / Prerequisites Dialog

The following diagram depicts the prerequisites flow:

For example, if the service is configured to require a phone number and OTP, the following pages will be displayed:

### Require Customer ID If the service requires a customer ID, the portal will ask the customer to identify himself. Depending on the "Customers" table self-authentication configuration, the portal will ask for key and validation fields or a customer ID and OTP.

To learn how to configure customer self-authentication, see: {% content-ref url="/spaces/8vfRpZGqpk7N0egaXMQ8/pages/wxhEV21ARVXI5HSy589Z" %} [The Customers Data Table](/guides/understanding-the-basics/process-management/the-customers-data-table.md) {% endcontent-ref %} ## **Data Collection** If the selected service's category configures one or more **required** fields, the portal will ask the customer to provide values for these fields. Example: Setting First Name and Last Name as required fields on the service category:

The portal will ask the customer to enter the information: