Custom fields

Add your own fields to any entity without waiting for a code change. Settings → Custom Fields, then pick the entity.

Where they show up

A custom field behaves like a built-in one. Once defined it appears:

• on the record's detail page
• as a selectable column in lists (and in saved views)
• in CSV exports
• in webhook payloads, so integrations get it automatically
• as a field forms can bind to

Types

Text, long text, number, date, checkbox, select, multi-select, and formula.

A formula field is computed rather than stored. It reads other fields on the same record. Because it's computed at read time it's always current, but it can't be edited directly and isn't available as a chart measure.

Two rules worth knowing

Custom fields are data, never behaviour. They store information; they can't change how the app works. Nothing branches on a custom field, so adding one can never break a process.

Changing a type is archive-and-recreate. You can't silently retype a field from text to number, because a value captured last year would then be reinterpreted under rules that didn't exist when someone typed it. Archive the old field and add a new one; the history stays honest.

Role visibility

A field can be limited to certain app roles. That's useful for wage rates or margin that shouldn't be on a field worker's screen. The restriction is enforced when the data is read, not merely hidden in the interface.