Kogenta Connect
Dashboards

Creating Dashboards

How to create and configure dashboards in Kogenta Connect.

Creating a dashboard involves linking workflows, choosing a layout, and adding widgets to visualize your data.

Creating a new dashboard

  1. Navigate to the Dashboards section
  2. Click the create button
  3. Give your dashboard a name and optional description
  4. Link one or more published workflows

Linking workflows

Dashboards get their data from workflows. When you link a workflow to a dashboard, all of that workflow's queries become available as data sources for your widgets.

You can link multiple workflows to a single dashboard, which is useful when you want to combine data from different pipelines in one view.

Pages

A dashboard can have multiple pages, each with its own layout and set of widgets. Pages let you organize related visualizations together while keeping the dashboard manageable.

For example, a retail analytics dashboard might have:

  • A Map page showing store locations and catchment areas
  • An Overview page with summary charts and KPIs
  • A Detail page with filterable data tables

Choosing a canvas type

Each page uses one of two canvas types:

Grid layout

A grid canvas provides a structured layout where you place widgets in rows and columns. Widgets snap to a configurable grid with adjustable column count and row height.

Map canvas

A map canvas provides a full-screen interactive map as the primary surface. Map layer widgets render directly on the map, and you can configure the initial view state (center coordinates, zoom level, pitch, and bearing). Layer controls and legends can be toggled and positioned on the map.

Dashboard width

Dashboards support two width modes:

  • Fluid — the dashboard stretches responsively within configurable minimum and maximum width constraints
  • Fixed — the dashboard is locked to a specific width

Width presets are available in both modes: narrow (960px), standard (1280px), large (1600px), and wide (1900px).

Adding widgets

Once you have a page with a canvas type, you add widgets to display data. Each widget is bound to a specific query from one of your linked workflows, and configured to visualize the data in a particular way (map layer, chart, table, etc.).

Container widgets

Container widgets let you group and organize other widgets within a page:

Card container

Groups widgets on a shared card surface. Cards support tabbed views, configurable padding, collapsibility, and custom header and footer colors.

Side panel

A collapsible panel attached to the edge of the page. Side panels can be placed on the left, right, top, or bottom, and displayed as either docked (fixed in layout) or floating (overlaid on the canvas). You can configure the panel width, whether it starts collapsed, and how content is arranged inside it (positioned on a grid or stacked vertically).

Side panels are particularly useful on map canvas pages, where you might float a panel with charts and filters over the map.

Stack

A simple container that arranges widgets in a fixed vertical or horizontal flow, without the grid-based positioning of other layouts.

Slicer panel

The slicer panel is a global filter bar that appears at the top or left of the dashboard. Unlike individual slicer widgets placed on the canvas, the slicer panel provides dashboard-wide filters that persist across pages.

Each slicer in the panel can be configured with a display style (dropdown, checkbox list, slider, date range, or hierarchy), default values, search and clear controls, and sort order.

Configuring default parameters

If your linked workflows have parameters, you can set default values for them at the dashboard level. This is configured in the Data Parameters section of the canvas settings.

Each linked workflow's parameters are listed with their name, description, and whether they are required. You can provide a default value for each parameter that will be used when the dashboard executes the workflow. This lets you reuse the same workflow across multiple dashboards with different parameter values without modifying the workflow itself.

On this page