from and to date tokens follow this range, and all applicable widgets update.
Filters: Select All environments and All channels at the top of the page to narrow the data by deployment environment and channel. Filter selections are reflected in the page URL, so you can bookmark a filtered view or share it with a colleague.
When a project has no dashboards, the page shows No dashboards yet. Select New dashboard to create your first one.

Dashboard actions
The dashboard picker switches between the project’s dashboards. The header shows how many dashboards exist and who created the current one.
Widget titles are typed by whoever builds them. Open the widget’s query before you trust its title. If a query returns a field with no values, its table or chart shows an empty column.
Build a widget
Each visualization on a dashboard is a widget. Select Add widget to open the widget editor, which opens as Untitled widget and stays open until you save or cancel.
To build a widget:
- Open a dashboard and select Add widget.
- On Query data, select a table from the table selector, for example
abl_platform.platform_events. - Write your SQL. Use the Schema panel to find column names and types.
- Select Run query. The result panel below the editor reports the rows returned.
- Open Preview rows to confirm the query returns what you expect.
- Open Visualize, choose a chart type, then map your fields to the axes.
- Select Save widget.
Query data
The SQL editor sits at the center of the tab, with the table selector, Schema for AI, and Run query above it. Schema for AI copies the selected table’s schema in a form an AI assistant can use to draft the query. Queries are scoped bytenant_id and project_id by default. Use the from and to date tokens when the widget should follow the dashboard date range. See Example of Query scoping.

Custom tags live in the
custom_dimensions column, a map of string keys. Read one in SQL as custom_dimensions['key'].
Label dimensions in a visual query
For tables that support the visual query builder, such as output item tables, give each grouped dimension a readable label so dashboard users don’t see raw field names. For example, label the dimensiondim_pnr as Booking reference.
Result panel
After you run a query, the panel below the editor holds the result. Switch between Preview rows and Visualization without leaving the result, so you can check the data and the chart against each other. The result reports five statistics.
Below the statistics, a chip for each column shows the data role the platform assigned it, for example
timestamp: time and rows: metric. These roles determine which columns are available to each axis in Visualize.
Preview rows displays the result as a table, one column per field in the result set. Columns from a visual query show their dimension labels.

Visualize
Visualize builds the chart from the result set. A status badge reads Ready when the current mapping produces a valid chart. Four tabs configure the visualization.
Widget API details
Each widget’s data is also available through the widget data API, so you can pull the same numbers into your own reports or scripts. The API details dialog shows the exact request the dashboard runs for the widget, with the dashboard’s current date range and active filters already applied.
Use the Filters table to check why a widget shows different numbers from the rest of the dashboard. A filter that doesn’t apply to the widget’s table appears in the list but doesn’t change the result.
Multi-select filters
A dashboard filter can accept one value or several. When you switch a filter to multi-select, the platform updates the SQL of every widget that uses the filter’s token, so the widget matches any of the selected values.
If a single-value token receives more than one value, the widget stops filtering on that field rather than silently using only the first value. Switch the filter to multi-select to filter on several values.
Example of query scoping
The platform scopes queries to the current tenant and project by default. Let us considerabl_platform.platform_events as the query table. Use the date tokens when a widget should follow the dashboard date range.
The following query counts events over time and follows the dashboard date range: