Columns
Columns define the fields in a Phormic table. Each column has a name, a type (e.g. text, number, date), and optional settings (required, default value, validation). Together, columns define the structure of every row in the table.
What is a column?
A column:
- Belongs to a single table.
- Has a name (e.g. “Title”, “Status”, “Due date”).
- Has a type that determines what kind of data it holds and how it is displayed and edited.
- Can be required or optional.
- Can have default values, validation rules, or options (e.g. for dropdowns).
When you add or edit a row, you fill in one value per column (according to its type).
Available column types
Phormic provides the following column types:
| Type | Description | Example use |
|---|---|---|
| Text | Short or long text. | Title, description, notes. |
| Number | Numeric values. | Quantity, price, score. |
| Status | One value from a defined set of options (e.g. workflow states). | New, In progress, Done, Blocked. |
| Timespan | Duration or time range. | Duration, time spent, deadline range. |
| Date | Date (and optionally time). | Due date, created at, deadline. |
| People | One or more users in the system. | Assigned to, reviewers, participants. |
| List | A list of options defined at table level (for this table only). | Category, priority, type. |
| Project list | A list defined at project level; same options can be used across tables in the project. | Category, priority, type (shared in project). |
| Files | File attachments. | Documents, images, attachments. |
| Owner | The user who owns or is responsible for the row. | Owner, responsible person. |
| Checkbox | Yes/no (boolean). | Completed, approved, active. |
| ID | Unique identifier for the row (typically auto-generated or system-managed). | Record ID, reference number. |
Note: List is defined per table. Project list is defined once per project and can be reused in any table in that project, so options stay consistent across the project.
Working with columns
Depending on your permissions you can:
- View column names and data in the table.
- Add new columns and choose their name and type.
- Edit column settings (name, type, required, default, options).
- Reorder columns (drag to change order).
- Hide or show columns in a view (without deleting them).
- Delete columns (if allowed; this may remove data in that column).
Column structure is usually edited by project owners or users with “edit table” rights.
Best practices
- Use clear, consistent names (e.g. “Due date” instead of “Date 2”).
- Choose the right type so that filtering, sorting, and validation work as expected.
- Use Status, List (per table), or Project list (shared in project) for fields with fixed options (e.g. workflow state, category).
- Mark as required only fields that must always be filled in.