Views

Views define how users browse, compare, open, and work with records inside a module. A module can define a default view so users start in the layout that best matches the main workflow.

Users can often switch between available views while working. The configured default view only controls the first layout shown when a module is opened.

Record-Based Views

Mixed View

The mixed view shows a record list and the selected record detail at the same time.

This is the standard pattern for modules where users browse several records and edit one record without losing their place in the list. It works well for master data, project records, people, organisations, tasks, and many other administration workflows.

Mixed View Horizontal

The mixed view can also be arranged horizontally.

This layout gives more width to tables and compact record details. It can be useful when users need to compare list columns while still keeping the selected record visible.

Single Record View

The single record view focuses on one record at a time.

This view is useful when the detail screen is more important than the surrounding list, or when the record contains enough information that the list would mainly distract from the editing task.

List View

The list view focuses on the table of records.

This view is useful when users need to scan, sort, filter, export, or compare many records. The usefulness of a list view depends heavily on well-chosen Queries and Column Selections.

Calendar View

Calendar Data

Some modules can be shown as a calendar.

Calendar views are useful when records represent scheduled items such as events, shifts, bookings, appointments, or screenings. The records need suitable date and time information, and the module needs to be configured so the calendar can read the correct fields.

Calendar Presets

Calendar modules can use presets to control how calendar information is grouped or displayed.

For example, a project might need a weekly calendar for general planning and a daily view grouped by location for operational scheduling.

Default View

Choosing the Default

The default view should match the way users usually start work in the module.

A module used for editing individual records will often start in a mixed view. A module used for comparison or export may start in list view. A planning module may start in calendar view when the schedule is the central working surface.

Switching Views

The default view does not have to be the only useful view.

Where several views are enabled, users can switch between them during work. This allows the same module to support different tasks without creating separate modules for every layout.