Skip to main content

Exporting dashboards

A static export captures a dashboard as a self-contained snapshot you can take outside Flynt -- for example, to publish a frozen report on your own site or hand a board pack to people who will never log in.

What an export contains​

The snapshot bundles everything needed to render the dashboard with no connection back to Flynt:

  • the dashboard's layout, including text blocks and groupings;
  • every card's chart definition and any client-side transform it applies;
  • the data rows, frozen at the moment of export. A dataset shared by several cards is included once; cards with their own direct query carry their rows inline.

Dataset SQL is deliberately not included. The export is data plus presentation, so you can hand it over without exposing the queries behind it.

If the dashboard uses parameters, you supply parameter values when exporting and the snapshot bakes in the rows those values produce.

Who can export​

Two gates apply:

  • You need view access to the dashboard -- any tier from Viewer (T1) up.
  • Your organisation's plan must include static export. It is part of the Pro plan and above; on the Free plan an export attempt is refused with an upgrade prompt. See Plans and billing.

How exports count toward usage​

Every export is recorded as a dashboard-export event. Administrators (T7+) can see the running day and month totals on the Plan & usage page. There is no cap by default, but if a limit has been set for your organisation, exports beyond it are refused until the day or month rolls over -- the refusal says how long to wait. See Usage limits.

Each export also appears in the organisation's audit log, including which dashboard was exported and by whom.

Availability​

There is no export button in the app yet. Exports are requested through the Flynt API using your normal signed-in credentials; the response is the snapshot itself, ready to feed a static rendering pipeline. An in-app export control is planned.