> 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/process-management/the-customers-data-table.md).

# The Customers Data Table

## The "Customers" Data Table

The Customers table is a built-in data table created when the organization is created. This table is used for storing the organization's customers.

### Customer Self-Authentication

The Customers table provides additional settings to control if and how customers can identify themselves on Kioksk and Portals.

The options are:

* **None:** self-authentication is not supported.
* **Field Validation:** The customer must enter the selected key field value and the value of another field stored on the record. The customer is authenticated if the validation value matches the value on record. \
  When selecting this option, you must specify the key and validation fields.
* **One-Time Password (OTP)**: The customer is required to enter the selected key field. The system will send an OTP to the customer's contact phone number and ask the customer to provide the password. The customer is authenticated if he provides the correct password. \
  When you select this option, you must specify the key field to use.\
  To use this option, the customer must have a mobile phone number stored in the Contact Phone Number field, and the organization must have a positive SMS balance.

Check the "Requires Customer ID" box in the service settings to require customer identification for a specific service.

## Data Table Webhook

The data table's "Query and sync remote data" webhook is used for integrating with 3rd party and legacy systems. When enabled, when a user searches for a data record, Cubu will call the webhook, fetch records from the remote system, and create or update a data record in Cubu's database.

To learn how to configure this advanced scenario, check out the Technical Guide:

{% embed url="<https://docs.cubu.com/guides/v/technical-guide/integration-guides/extending-cubu-with-webhooks/data-table-webhooks>" %}

## See Also

{% content-ref url="/spaces/8vfRpZGqpk7N0egaXMQ8/pages/YfXoNTrBYAIkayXggvzm" %}
[Managing Data Tables](/guides/admin-tools/service-and-process-configuration/managing-data-tables.md)
{% endcontent-ref %}

{% content-ref url="/spaces/8vfRpZGqpk7N0egaXMQ8/pages/F04xO0nuOB1mor24MztQ" %}
[Managing Fields](/guides/admin-tools/service-and-process-configuration/managing-fields.md)
{% endcontent-ref %}

{% content-ref url="/spaces/8vfRpZGqpk7N0egaXMQ8/pages/KvjTBfUcfeHAjiVUiYGr" %}
[Walk-in Services Settings](/guides/admin-tools/service-management/walk-in-services-settings.md)
{% endcontent-ref %}

{% content-ref url="/spaces/8vfRpZGqpk7N0egaXMQ8/pages/ECmSkVLBTqS0tBCWx9r8" %}
[Appointment-based Services Settings](/guides/admin-tools/service-management/appointment-based-services-settings.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.cubu.com/guides/understanding-the-basics/process-management/the-customers-data-table.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.