Saved

Where what you keep from the workbench lives, in three tabs. Boards: every board is a collection of saved tiles, and every tile re-runs its own query on each open, so the numbers are live rather than snapshots. Reports: a saved question that lives on one board, with a description and a version history. Insights: a question kept whole, its editor and its chart, reopened in the workbench with everything as it was. Every tab searches by name; boards are created, renamed, duplicated and deleted, reports renamed, moved, duplicated and deleted with an Undo, and insights renamed, pinned to a board or deleted.

Boards

Every board in the project on the Boards tab, searchable by name, with the count in the page head describing the whole library rather than the narrowed view. New board names a board and opens it empty; a board's row menu renames, duplicates or deletes it, and deleting asks first because a board's tiles are the only copy of their saved questions. How the tab presents, as cards, rows or a table, is a stored preference per person, picked on the tab's own bar. Switching arrangements starts on the Growth plan; the Starter plan reads cards.

Reports

A report is a saved question that lives on one board, under a name and a description, with every change kept as a version. It is saved from the workbench's Save menu, Save as report, in two steps: first the name and the description, then the board it lives on, picked from a searched list three rows tall with New board beneath. The Reports tab lists every report in the project as a card: the name opens it in the workbench, the description follows, and the meta line says which board it is on, its version and when it was last updated. Search matches the name and the description. The card's menu opens it, renames it, moves it to another board, duplicates it or, below the divider, deletes it. Deleting asks first and takes the versions with it; a delete or a move lands at once and the snackbar says so with Undo, the one way back, and a deleted report is purged an hour later. On its board a report is a tile marked Report with its version, in the primary tone, and Open report leads its menu; a pinned tile is marked Insight. Removing a report tile from its board is the report's delete, with the same Undo. Under the workbench card the version strip names the current version, who saved it and when; Show history unfolds every version, what changed, by whom and when, three entries in view, with Restore beside every one but the current, and a restore writes a new version copying the chosen one rather than rewriting history.

A board and its tiles

Each tile is one saved question: its title, the current total, a signed delta against the preceding window and a sparkline of the series. Tiles are added by asking a question in the Analytics workbench and pinning the result here; the pin dialog offers every existing board and a new one. A trend tile carries the whole query forward: every metric, any formula, its breakdowns and its compared period, so a re-run always answers exactly what was pinned. A tile that fails to load says so on the tile, with its own retry, rather than poisoning the board; Refresh re-runs every tile at once, and a tile's menu renames it, switches it between standard and wide widths, moves it along the grid, or removes it.

Insights

An insight is a question kept whole: the editor as it was composed, its analysis type and the chart type it was read in, under a name. It is saved from the workbench's Save menu, As an insight, and reopened from here or from the address the workbench carries as ?insight=, with the editor and the chart restored. The card names the analysis type on a chip, prints the question in words with its chart type, and says when it was last saved. Its menu opens it, renames it, pins it to a board as a tile titled after it, or deletes it. Deleting asks first, and the boards that carried it as a tile keep their tile, because a tile is its own copy of the query. Search matches the name and the words. An insight with a watch carries a Watching chip after its name, in the warning tone while its bound is crossed.

Copy to… on the row opens the configuration copy with this object already ticked; see Projects, Copying configuration.

Where this meets the API

The concept behind the three tabs is the Analytics pillar. On the wire: the Boards tab is the dashboards query, the Reports tab is reports and the Insights tab is insights; boards change through createDashboard, updateDashboard and deleteDashboard (pinning a tile is an updateDashboard carrying the new tile), insights through createInsight, updateInsight and deleteInsight. A report is saved through createReport, read alone through report, changed through updateReport, renameReport, describeReport and moveReport, copied through duplicateReport, deleted through deleteReport and brought back through restoreReport; its history is reportVersions and Restore is restoreReportVersion, which writes a new version copying the chosen one. A report's public link is read through reportPublicLink, turned on or given a new stop day through setReportPublicLink and turned off through turnOffReportPublicLink, and reportShareChanges streams each change; shareReport sends it to teammates, with a note, by email and push. People talk about a report in threads, on the whole report or on one point of it: reportCommentThreads reads them, each with its first comment and latest two replies, reportCommentEarlierReplies reads the replies before those twenty at a time, startReportCommentThread starts one, replyToReportCommentThread answers it, resolveReportCommentThread and reopenReportCommentThread close and open it again, an author changes their own words through editReportComment and deleteReportComment, reactions come and go through addReportCommentReaction and removeReportCommentReaction, and reportCommentChanges streams each change. A report's tile carries only its reportId, and the board read fills the tile from the report, so every tile renders by running its query through runQuery (GraphQL reference). A run that names its report through reportId refreshes that report's public link when the query it ran is the one saved.