Field visibilities

Why this matters

A field can appear in eight distinct contexts: the list (table), the detail, the create form, the edit form, the summary, the related-to-parent tab, kanban, cards. Visibilities let you decide which fields appear in which contexts. Without this, every field appears everywhere and forms become unmanageable.

The eight contexts

Context	Function	Where it's used
list	index	List view (table columns)
details	show	Detail view (visible fields)
form_create	create	Form when creating a new record
form_edit	edit	Form when editing an existing record
summary	show	Summary section of the detail
related_to_parent	index	Parent's related tabs
kanban	index	Kanban view (card fields)
cards	index	Card view
cards_related_to_parent	index	Cards in related tabs

Configure a field's visibility

1. Open the module → Visibilities tab.
2. Find the field in the list.
3. Check/uncheck the boxes for each context.
4. Save.

Why it's not the same as permissions

• Visibility = is this field rendered in this context? Module-wide decision.
• Field permission = is this user allowed to see/edit this field? Per-role/profile decision.

A field can be visible in form_edit context (visibility allows it) but invisible to a specific user because their profile restricts it. Both layers work together.

Typical cases

• Internal notes — visible in details and form_edit, invisible in list (don't want long notes in the table).
• Folio — visible in list and summary, invisible in forms (auto-assigned).
• Quote total — visible in list, details, summary, cards, kanban.
• Disqualification reason (lead) — visible only when status is "Disqualified", controlled via conditions (later).

Field groups

To organize many fields in the form, group them with field groups (field_groups):

1. Create a group (for example, "Personal data", "Documents", "Address").
2. Assign fields to the group.
3. In the form, fields appear in collapsible sections by group.

This turns the wall-of-50-fields into manageable sections.

Watch out for

• Default visibility is "every context". If you create a new field and don't configure visibility, it appears everywhere. Configure immediately.
• Removing a field from list doesn't delete it — it just stops appearing in the table column. Data stays in the record. If you later want to show it in saved filters, re-check.
• Verify after mass changes. If you modify visibilities for many fields, review the list view before calling it done — a bad change can leave the table without useful columns.

Where to next

• Module relationships — the related_to_parent context depends on relationships.
• Fields — to understand which fields you'll configure.