Field visibilities

Why this matters

A field can appear in eight distinct contexts: list, detail, create form, edit form, summary, related-to-parent tab, kanban, cards. Visibilities let you decide which fields appear in which contexts.

The eight contexts

Context	Function	Where it's used
list	index	List view (columns)
details	show	Detail view
form_create	create	Create form
form_edit	edit	Edit form
summary	show	Summary section
related_to_parent	index	Parent's related tabs
kanban	index	Kanban view
cards	index	Card view

Configure visibility

1. Open the module → Visibilities tab.
2. Find the field, check/uncheck contexts.
3. Save.

Visibility vs. permissions

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

Both layers work together.

Typical cases

• Internal notes — visible in details and form_edit, invisible in list.
• Folio — visible in list and summary, invisible in forms.
• Total — visible in list, details, summary.

Field groups

To organize many fields in the form, group them with field groups. They appear as collapsible sections.

Watch out for

• Default visibility is "every context" on field creation. Configure immediately.
• Removing a field from list doesn't delete it.
• Verify after mass changes.

Where to next

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