Data table field types

Every column in a data table has a type. The type is permanent once the field is created.

Type	What it holds	Can be encrypted	Masked when encrypted
`text`	Short single-line text.	Yes	No
`long_text`	Multi-line text, for notes and descriptions.	Yes	No
`number`	A number, whole or decimal.	No	No
`currency`	A monetary amount.	No	No
`date`	A calendar date with no time.	No	No
`datetime`	A date and a time.	No	No
`boolean`	True or false.	No	No
`single_select`	One choice from a list you define.	No	No
`multi_select`	Any number of choices from a list you define.	No	No
`email`	An email address.	Yes	Yes
`phone`	A telephone number.	Yes	Yes
`url`	A web address.	Yes	No
`status`	A workflow state, such as new, in progress or done.	No	No
`json`	Structured data, for values that do not fit another type.	No	No
`auto_increment`	A number that increases automatically for each new record.	No	No
`uuid`	A unique identifier generated automatically.	No	No
`contact_id`	A reference to the contact a record belongs to.	No	No
`relation`	A link to a record in another table.	No	No
`name`	A person's name.	Yes	Yes
`nric`	A national identity number.	Yes	Yes
`address`	A postal address.	Yes	Yes
`whatsapp_id`	A contact's WhatsApp number.	Yes	Yes
`telegram_id`	A contact's numeric Telegram ID.	No	No
`telegram_handle`	A contact's Telegram username.	No	No
`asset_id`	A reference to an uploaded file or image.	No	No

Can be encrypted — the field can be created with field-level encryption. That choice is permanent, and it limits how the field can be searched — by a whole value, by a whole word, or not at all. See finding an encrypted field later.

Masked when encrypted — values are shown partially hidden (j***@x.com) and revealed only through an explicit, audited action. This applies to encrypted fields; note that telegram_id and telegram_handle are treated as personal data but cannot be encrypted.

Data table field types

Related pages

On this page