Styles
Styles rules make data legible at a glance: overdue rows turn red, completed tasks get a strikethrough, the "Approve" button glows green only while a record is pending. Each rule picks a table, an optional condition, and the fields or action buttons it colors.
What a rule can change
| Setting | Options | What it does |
|---|---|---|
| Text color | — | Tints the value (or the action's label and icon). Any color — dark mode readability is handled automatically. |
| Background | pill / fill | A badge around the value, or the whole cell. On action buttons the background fills the button. |
| Icon | — | Placed before field values; replaces the action's configured icon. Takes an optional color of its own — unset, it follows the text color. |
| Text style | bold / italic / strikethrough | Classic emphasis — strikethrough for done, bold for urgent. |
Always, or by formula
A rule with no condition styles its targets on every row. Add a formula — [Status] = "Blocked", [Due] < TODAY()— and it styles only the rows where the formula is true. Conditions use the table's own fields, like validation rules, so they evaluate instantly as data changes.
When rules overlap
Rules apply top to bottom, and each attribute merges separately: a rule that only sets an icon composes with one that only sets a color. When two rules set the same attribute on the same row, the one lower in the list wins — drag rules to reorder.
- Styles apply everywhere a value renders: tables, cards, record pages, kanban, calendars, timelines — and public links.
- On forms and inline-editable cells, the field's label carries the style; the input stays neutral so rule colors never look like errors.
- Styles never hide anything — visibility stays with visibility conditions and roles.