Custom fields
Custom fields let you shape items to fit your process. They are Monday-style columns, configured per organization, and rendered dynamically across views, forms, and the portal.
Available field (column) types
| Type | Use it for |
|---|---|
| Status | A colored, single-select state (its own set of labels). |
| Person | Assigning a user. |
| Date | A single calendar date. |
| Timeline | A start-to-end date range (drives Timeline/Gantt). |
| Number | Quantities, counts, amounts. |
| Formula | A computed value derived from other fields. |
| Dropdown | Single- or multi-select from a defined list. |
| Checkbox | A simple yes/no flag. |
| Files | Attached documents or images. |
| Link | A URL. |
| Rating | A score (e.g. stars). |
| Dependency | A relationship to another item (blocks / blocked-by). |
How custom fields behave
- Per organization and configurable — you decide which fields exist and how they are labeled. Nothing is hardcoded.
- Rendered dynamically — once you add a field it appears automatically in views and can be surfaced in forms and the portal; no rebuild required.
- Usable everywhere — filter, sort, and group by custom fields in Views, summarize them in Dashboards, and collect them through intake forms.
Adding a custom field
- Open Settings → Custom fields.
- Choose a type from the table above.
- Configure it (label, options for dropdown/status, formula expression, etc.).
- Decide whether it is portal-visible if end-users should see it.
Portal-visible fields
Some custom fields can be marked portal-visible so contacts see relevant details on their tickets in the portal. Keep internal-only fields hidden.
Tips
- Use Timeline fields to power Gantt scheduling.
- Use Formula fields to derive roll-ups instead of maintaining numbers by hand.
- Only expose the custom fields end-users actually need in the portal.