Once the dashboard is ready, you export it (XLSX, CSV, PNG, PDF, PowerPoint, printing) and distribute it (public link, TV link, embed, email/WhatsApp subscription, alerts). Every output respects RLS + PII masking and a confidentiality stamp. Examples use the synthetic workspace Comércio Aurora Ltda.
Step-by-step guides
This page is the technical reference. For the on-screen path, see Dashboard header actions, Read a dashboard, TV link and Subscriptions and alerts.
Export XLSX (Excel)#
- What it is — exporting the dashboard to Excel, in SUMMARY and DETAIL modes.
- When to use it — sending the numbers to people who work in Excel. On screen: the Excel button in the header (summary) or More actions ▸ Export Excel: Summary (as on screen) / Underlying data (detail).
- How it works — reads the snapshot with RLS + PII applied; a sample badge when truncated; a confidentiality stamp in 3 places; audited.
- Prerequisites — a snapshot available; export permission.
- How to validate — export in DETAIL mode; open the file and confirm the data, the sample badge (if truncated) and the confidentiality stamp.
- Limits and caveats — respects the snapshot ceiling; PII masked according to the requester.
- Sample data (synthetic) — a "Revenue by state" spreadsheet: SP=250, RJ=90, MG=140.
- Evidence — XLSX export (summary/detail modes, sample badge, confidentiality stamp) covered by a deterministic suite and an export contract.
Export CSV (per visual)#
- What it is — a CSV of one visual, in the pt-BR Excel dialect.
- When to use it — taking a chart's series to another tool. On screen: right-click the chart ▸ Export this visual as CSV.
- How it works — in the browser;
;separator, CRLF line breaks, comma as the decimal separator. - Prerequisites — a visual with data.
- How to validate — export the CSV of "Revenue by category" and open it in pt-BR Excel without broken columns.
- Limits and caveats — it's per visual (not the whole dashboard). To just look at the rows, without downloading, use See records (underlying rows) in the same menu (up to 200 rows).
- Sample data (synthetic) —
categoria;receita/Bebidas;250. - Evidence — CSV generation in the pt-BR Excel dialect (
;separator, CRLF, comma decimal) covered by a deterministic suite.
Export PNG (per visual and per page)#
- What it is — a PNG image of a visual or of the whole page.
- When to use it — pasting a chart into a presentation or email. On screen: right-click the chart ▸ Save as image; on the public link, the Save as image button above the dashboard saves the whole page.
- How it works — in the browser; the chart is drawn into an image at double resolution.
- Prerequisites — a rendered visual.
- How to validate — export a visual's PNG and check the generated image.
- Limits and caveats — the image is generated by your browser; sharpness may vary between browsers.
- Sample data (synthetic) — a PNG of "Revenue by state".
- Evidence — the PNG export flow is covered by a deterministic suite (name/structure); rasterization itself isn't testable in CI.
Export PDF (on-demand dashboard and scheduled report)#
- What it is — an on-demand dashboard PDF and a scheduled report PDF.
- When to use it — sending a faithful snapshot of the dashboard to people who don't access the platform. On screen: the PDF button in the header, or More actions ▸ Export PDF: PDF. When the PDF doesn't come out, a tooltip explains why and points to Print preview ▸ Print / PDF as an alternative.
- How it works — a cloud rendering worker prints the page; for the on-demand dashboard, the credential is an ephemeral embed token (5 min, scoped to 1 dashboard, with the session's RLS), so the worker prints exactly the requester's slice (PII masked, unpublished dashboard refused); audited; anti-IDOR download.
- Prerequisites — datalake and reports worker configured and a plan with PDF enabled (Business+), and the dashboard published with the share link turned on (an unpublished dashboard is refused, with a message pointing to Print preview › Print / PDF). Without them, nothing is generated.
- How to validate — with the rendering worker configured, generate the dashboard PDF and confirm the same slice as on screen + the confidentiality stamp.
- Limits and caveats — depends on the rendering worker; generation time grows with the number of pages in the dashboard.
- Sample data (synthetic) — a PDF of "Aurora Varejo — July/2026".
- Evidence — the slicing logic (ephemeral embed token, session RLS, PII masked, anti-IDOR) is covered by a deterministic suite; real generation depends on the cloud print worker.
Export PowerPoint (PPTX)#
- What it is — exports the dashboard to PowerPoint: one dashboard page = one slide (16:9).
- When to use it — building the executive presentation from the dashboard. On screen: the PPT button in the header or More actions ▸ PowerPoint: Presentation (.pptx).
- How it works — a clone of the XLSX pattern (session / anti-IDOR / secure view / audit); data → a native shape when possible (KPI = number box; bar/line/pie = native charts; table/matrix/maps/exotic visuals = a table with a cap + SAMPLE badge); proportional grid; theme colors; confidentiality stamp in 3 places. Deterministic: same input + same clock → identical bytes.
- Prerequisites — a snapshot available; export permission.
- How to validate — export the PPTX of a 2-page dashboard and confirm 2 slides
- a title slide with the snapshot date.
- Limits and caveats — the appearance may vary between versions of PowerPoint and other presentation readers.
- Sample data (synthetic) — a "Revenue by state" slide (SP/RJ/MG).
- Evidence — deterministic PPTX generation (identical bytes for the same input) covered by a suite that validates the internal XML; the appearance when opened in Office isn't tested.
Printing#
- What it is — the Print preview: the dashboard page the way it comes out on paper, with header and footer.
- When to use it — a quick paper copy or a PDF through the browser, including when the plan doesn't include on-demand PDF.
- How it works — the Print preview button in the header (or under More actions, on narrow screens). In the preview, Print: chooses All, Current page only or individual pages; Print / PDF opens the browser's print dialog; Close (Esc) goes back. Editors can adjust the Header and footer. On the public link, the button is Print.
- Prerequisites — none.
- How to validate — open the preview of a 3-page dashboard, check only 2 and confirm the printout comes out with 2 sheets at the configured size.
- Limits and caveats — the final result depends on the browser.
- Sample data (synthetic) — printing the "Summary" page.
- Evidence — printing through the browser with dedicated print styles.
Public links and embed#
- What it is — an unguessable public link (
/d/[slug]), open web publishing (/painel/[slug]) and embedding with an HMAC token in third-party portals. - When to use it — sharing a dashboard outside the platform without giving a login.
- How it works — links read the snapshot with PII always masked and
at no cost to the visitor; open web publishing requires typing the name + warnings and is
audited; embedding uses an HMAC-SHA256 token (15-min TTL, 12h ceiling), timing-safe,
with Origin/Referer checks and a
frame-ancestorsCSP based on an allowlist. - Prerequisites — publish the dashboard; for embedding, the origin on the allowlist. On screen: More actions ▸ share (the 1 · Secret link, 2 · Embed in your app and 3 · Publish to the web (indexable) cards).
- How to validate — generate the
/d/<slug>link, open it anonymously and confirm the data with PII masked; embed it in an allowlisted portal and confirm it loads. - Limits and caveats — public links are permanent by design (no password and no expiration) — cutting off access means generating a new link; the embed allowlist is platform-wide, not per workspace.
- Sample data (synthetic) —
/d/aurora-vendas-julhoshowing SP/RJ/MG. - Evidence — public links, open web publishing and HMAC-token embedding
(TTL, timing-safe, Origin/Referer checks,
frame-ancestorsCSP) covered by a deterministic suite.
TV link (TV/kiosk mode)#
- What it is — the secret link with
?tv=1: the dashboard in full screen, with no menus, with the page scaled to fit the whole 16:9 screen, pages that rotate and data that refreshes on its own. - When to use it — a TV or wall monitor in the store, the factory, the sales area.
- How it works — copied under Share ▸ TV link ▸ copy
TV link. The owner configures it in the editor (Page ribbon ▸ TV ▾): rotating
pages, Seconds on each page (10–600, default 30), Refresh data
every (min) (minimum 1) and Show clock and date in the corner; and can
arrange a dedicated TV layout. Tooltip and drill-through pages are left out
of the rotation by default. The link accepts
tvIntervalo,tvRefreshandtvRelogio=0|1, which take precedence over the configuration, and combines with?f=. If the browser refuses automatic full screen, ⛶ Full screen appears. - Prerequisites — a published dashboard (the TV link is the secret link).
- How to validate — open
/d/<slug>?tv=1in a 1920×1080 window and in another at 1366×768: the same drawing fills both screens without scrolling; the page switches at the configured interval. - Limits and caveats — the same as the secret link (no password or expiration); it doesn't work inside the system or in embeds.
- Sample data (synthetic) — "Today's sales — Downtown Store" rotating 3 pages every 45 s with a clock.
- Evidence — rotation, interval limits, page selection and sheet scaling covered by a deterministic suite; full screen and the cursor depend on the browser.
Email subscriptions#
- What it is — the owner schedules (day of the week + time) the dashboard's delivery by email, with KPIs + link + attached XLSX; readers can also subscribe.
- When to use it — sending the weekly summary to leadership automatically.
- How it works — in the editor, Tools ▸ Publishing ▸ Send automatically (subscription) ▸ Save subscription; the trigger is checked every 5 minutes; per-recipient RLS adds to the Per-recipient filter (never widens it); the link is suppressed when there's a row filter; More actions ▸ Deactivate pauses it; there's a delivery ledger. With scheduled deliveries, readers see Get by email in the header and join or leave the list on their own (Subscribed ✓ (cancel)).
- Prerequisites — the platform's email sending configured, with a verified domain; without it, sending doesn't happen and the record is marked as a failure.
- How to validate — schedule a subscription for
ana@example.com, wait for the time and confirm the email with KPIs + attachment. - Limits and caveats — every send is logged; if the email fails, the log shows the failure.
- Sample data (synthetic) — a "Weekly summary" subscription on Mondays at 8 a.m.
to
maria@example.com. - Evidence — scheduling, per-recipient RLS, link suppression under a filter, reader subscription and delivery ledger covered by a deterministic suite; real delivery depends on a verified email domain.
WhatsApp subscriptions and alerts#
- What it is — sending a dashboard/alert via WhatsApp through the official WhatsApp channel. On screen: the subscription's WhatsApp field, the alert's Channel, or Send via WhatsApp in the dashboard menu under BI → Workspace.
- When to use it — notifying on WhatsApp when a KPI flips, or sending the summary.
- How it works — the official channel (the product's number + WABA, within the Terms), with an approved template to open the 24h window and the recipient's consent.
- Prerequisites — the WhatsApp channel configured on the platform, an approved template and the recipient's consent.
- How to validate — with the envs and the template approved, trigger an alert and confirm the message on the consenting number.
- Limits and caveats — depends on credentials and an approved template; without them, the message isn't sent.
- Sample data (synthetic) — the alert "Today's revenue below target" sent to a consenting test number.
- Evidence — official channel (Cloud API), recipient consent and delivery routing covered by a deterministic suite; real delivery depends on credentials + an approved template.
"AI Analyst" scheduled reports#
- What it is — a periodic report with an AI narrative (headline, executive
summary, highlights, anomalies, recommendations) and a public page
/r/[slug]. - When to use it — an "analyst" who sends the reading of the numbers on schedule.
- How it works — a time-zone-aware cron; the queries are frozen at creation
(≤500 rows/query); the narrative is generated by AI and stored; idempotent via
@@unique([reportId, scheduledFor]); delivery by email/WhatsApp; optional PDF. - Prerequisites — a plan with AI and channels configured. On screen: AI → Reports ▸ New report — see Reports screens.
- How to validate — create a weekly report, trigger the cron and confirm the
/r/<slug>page with the narrative and the delivery. - Limits and caveats — the narrative depends on an AI key; snapshot rows travel to the LLM provider (see the platform's AI caveats).
- Sample data (synthetic) — an "Aurora weekly sales" report with a headline about SP leading.
- Evidence — report execution (queries frozen at creation, idempotency per schedule) and rendering covered by a deterministic suite.
Alerts (threshold, anomaly, history, webhook)#
- What it is — alerts per visual (threshold) and per report (% anomaly), with history, backtest and a signed outbound webhook.
- When to use it — notifying when a KPI crosses a threshold or the number departs from the pattern. On screen: in the editor, with the chart selected, Format ribbon ▸ Alert (Notify when, Measure, Summarize by, Channel, Recipient); for reports, Smart alerts in the New report wizard.
- How it works — an absolute threshold (
>,>=,<,<=) evaluated on refresh; it fires only on the transition to breached (re-arms once back to normal); anomalybelow/above/drop_pct/spike_pctvs a baseline with a cooloff; email / WhatsApp / webhook channels (POST to the customer's system, HMAC-SHA256 withX-Ingestia-Signature, retry). Firing history and rule backtest. - Prerequisites — the Business+ plan for alerts; a configured channel (for a webhook, an https URL on the customer's side).
- How to validate — configure "Today's revenue < 1,000 → webhook", force the breach and confirm the signed POST + the entry in the history.
- Limits and caveats — evaluation happens on the dashboard refresh (there's no dedicated alert cron). Alerts tied to a target don't exist: the Targets screen was removed from the product on 09/26/2026 — the target becomes a measure over your targets table, and alerts are per visual.
- Sample data (synthetic) — the threshold "Receita < 1,000" with an actual of 900.
- Evidence — threshold/anomaly evaluation, firing on transition, history, backtest and signed webhook (HMAC) covered by a deterministic suite.
Last reviewed: 2026-10-03.