Common Settings

All field types share a set of common settings organized into two tabs: Basic Settings and Advanced Settings.

Primary configuration for the field.

Setting	Description
Field Name	Required. Unique identifier in your code and database (e.g., `firstName`, `status`).
Input Type	Required. Determines validation behavior and UI rendering (e.g., Text, Email, Date).
Default Value	Pre-fills new records when no value is provided.
Display Label	Human-readable label shown in forms. If empty, the Field Name is used.
Sort Order	Controls field position in lists and forms. Lower numbers appear first.
Icon	Visual identifier for the field in the Studio UI.
Status	Toggle. When disabled, the field is excluded from generated code.
Required	Makes the field mandatory for form submissions.

note

Default Value is not available for JSON, Auto Generated, System Generated, or File input types.

Additional configuration for validation, visibility, and automation.

Setting	Description
Description	Documentation for developers and content editors about the field's purpose.
Form Visibility	Options: Add (Create only), Edit (Update only), or Both (Default).
DB Field Name	Overrides the database column name if a different schema name is required.
Faker Type	Generates realistic test data (e.g., Names, Emails, Addresses).
Primary Key	Marks field as the record's unique identifier. (One per collection).
Use as Index	Creates a database index to optimize query performance.
Unique	Prevents duplicate values across all records in the collection.

info

Some settings are only available for specific field types. For example, Primary Key is limited to Single Line, Number, and Auto Generated fields.

Performance: Enable Use as Index for fields frequently used in filters.
Testing: Configure Faker Type to quickly populate your database with mock data.
Identity: Mark a UUID or ID field as Primary Key.

Deprecated

Populate from Logged-In User has been moved to the Areas section where it can be configured per-area for better flexibility.

Related​