Custom fields

Custom fields define the structure of a project and control what each row tracks.

Columns define the project schema

Picrowd projects are schema-based. The fields in one project do not have to match the fields in another project. This lets each workflow track what matters without forcing every team into the same setup.

Column types

Type / What it holds

Contact / A person, linked to the people directory

Company / A company or organization

Filter / The status values that drive Cards and the status filter; each project defines its own

Email / An email address

Phone / A phone number

Money / An amount with a currency

Ping / Follow-up reminders: several per cell, each with an optional time, length, name, and AI commands

Text / Free-form text

Last Comment / A preview of the latest note, with a thumbnail and count when it has attachments

Number / A whole number, decimal, or percentage, with an optional progress meter

Progress / A checklist with an automatic progress bar; can run AI commands when it completes

Formula / A value computed from other columns

Web Link / A URL

Color / A color label

Flag / Bright colored option labels, useful for priority

Tags / Hashtag labels

Last Active / The date of the record’s last activity

Date/time / When the record was created and last updated; present in every project and hidden by default

Files / Attachments that belong directly to the field

Formulas

A formula references other columns by name in curly braces, for example {Price} * {Quantity}, and supports IF, ROUND, ABS, MIN, MAX, MOD, FLOOR, CEIL, SQRT, EXP, LOG, and the trigonometric functions. Formula values update as the referenced fields change.

Changing fields later

You can rename, hide, reorder, pin, resize, and delete columns. Compatible field types can be converted instead of rebuilding the project from scratch; values that cannot be mapped to the new type are cleared, and Picrowd tells you before it happens.

Use conversion carefully when a field already contains important data. Check a few rows after changing a field type to make sure the result still reads correctly.

Field discipline

  • Add fields people will scan, sort, filter, or update
  • Remove fields that no longer help the workflow
  • Prefer short labels that make sense in a table
  • Use person and company fields when contact context matters
  • Use one Filter column for the workflow stage so Cards and the status filter stay meaningful