Dashboards and apps

Dashboards and apps are published workflow results.

Underdata turns reviewed workflow outputs into dashboards and data apps that business users can use without editing the underlying logic. The published surface stays connected to the workflow that produced it.

Published business question

What should the revenue team see every Monday, and which reviewed workflow should refresh it?

Publish from reviewed work

A dashboard or data app should not be detached from its evidence. Underdata keeps the source workflow, reviewed answer, and publish state connected.

  • Source workflow attached
  • Reviewed answer visible
  • Refresh path tied to the run

Give business users controls

Published outputs can include the filters, metrics, tables, charts, and actions that business teams need to explore the answer safely.

  • Filters and date ranges
  • Metrics, tables, and charts
  • Actions shaped around the workflow

Keep reruns governed

When the business needs a new period or segment, the app points back to the workflow so the result can be rerun and reviewed instead of rebuilt.

  • Rerun from approved logic
  • Review before broad sharing
  • Reusable app for recurring work

From workflow to published app

  1. Review

    Confirm the workflow answer and supporting evidence are ready.

  2. Shape

    Choose the filters, metrics, tables, charts, and context users need.

  3. Publish

    Release the dashboard or data app from the governed workflow.

  4. Use

    Let business teams explore the answer without editing source logic.

  5. Refresh

    Rerun the workflow when the operating cadence repeats.

What gets published

Executive reviews that preserve the reasoning behind the number.

Operational views that business users can filter and revisit.

Data apps that keep recurring decisions connected to governed workflow logic.

Publish the answer your team already repeats.

Start with one recurring report or operating review, then define the workflow and published app it should become.