Dashboard

Dashboard is the operational starting view in Comers Core.

It brings selected information from Core into one configurable overview so users can see the state of the business context they are currently working in without opening every module separately.

Widget-based overview

Dashboard is built from widgets.

A widget represents one focused view of operational information. Depending on the capabilities currently available, widgets can show information such as sales activity, order metrics, connection state, or other Core data.

The available widget catalogue can change as Comers modules evolve. A Dashboard should therefore be treated as a configurable view over Core rather than a fixed report with a permanent set of metrics.

flowchart TD
    C[Current business context] --> D[Dashboard]
    O[Orders and commerce data] --> W[Widgets]
    I[Integrations and operational state] --> W
    W --> D
    D --> U[User operational overview]

Business context matters

Dashboard data follows the business context selected in Comers.

When you switch between available Sellers or sales accounts, widgets that depend on that scope can show a different operational picture.

Before comparing values or acting on a metric, verify the context shown in the workspace.

Choose the widgets you need

Where Dashboard configuration is available, you can choose which supported widgets should be visible.

This lets different users focus the starting view on the operational information that matters to their work instead of requiring everyone to use the same layout.

The presence of a widget does not grant access to data that the current user is not authorized to read.

Arrange the layout

Dashboard supports an editable layout.

You can arrange the enabled widgets and save the resulting layout. During editing, changes can be saved, discarded, or reset according to the controls available in the interface.

This makes the Dashboard useful as a personal working surface while the underlying business records remain in their authoritative Core modules.

Refreshing data

Dashboard can request a refreshed view of its current data.

A widget still depends on the source module or integration that supplies its information. Refreshing the Dashboard does not create missing source data or bypass a delayed external synchronization.

Dashboard is not the source of truth

Use Dashboard to notice trends, workload, or conditions that deserve attention.

For detailed work, open the module that owns the underlying record, such as Orders, Warehouse, Messages, or another relevant Core area. The Dashboard summarizes operational context; it does not replace those workflows.