Dashboards

Dashboards are modules that do not follow the classic pattern of many records with standard create, read, update, and delete workflows.

They are still shown as modules in the application navigation, but they present configured content directly instead of opening with a record list and selected record detail.

Dashboard Purpose

Summary Views

A dashboard can bring together important information from different parts of the application.

For example, it might show recent submissions, open tasks, counts by status, upcoming events, or links to frequently used workflows. The goal is to give users a useful starting point without requiring them to open several modules one after another.

Workflow Hubs

A dashboard can also act as a workflow hub.

This is useful when a group of tasks belongs together but does not fit neatly into one database entity. A dashboard might combine tables, buttons, explanatory content, and related links that guide users through a particular process.

One-Record Areas

Some dashboard-style modules are used for information that behaves more like a fixed page than a list of records.

For example, an application might have an overview area, a settings-like project page, or a reporting page where users do not need to create and select individual records.

Dashboard Structure

Components

Dashboards are built from the same component system as record detail screens.

They can include layout components, tables, buttons, media, text blocks, and other configured content. The individual component types are covered in the Components section.

Navigation

A dashboard should have a clear place in the module navigation.

Dashboards often work best near the modules they summarise or support. If a dashboard is mainly an administrative or reporting area, it may belong near other supporting modules rather than near day-to-day record modules.

When to Use a Dashboard

Useful Cases

A dashboard is appropriate when users need a curated working surface rather than a standard record browser.

This usually applies when the page combines several sources of information, presents summary information, or gives access to a set of actions that belong together.

Boundary with Modules

A dashboard should not replace a normal module when users mainly need to browse, create, edit, and manage records of one type.

In that case, a conventional module with a suitable default view, queries, and column selections is usually clearer.