Leaderboards That Never Go Stale

Pay-as-you-go from your credit wallet, billed per active board per month. There is no per-seat charge and no floor. Archived boards are not billed — archive one and it drops out of the next month's draw; restore it and it counts again.

Every visualization carries a policy — full names, first name plus last initial, or fully anonymized ranks — with a tenant-wide default for new ones. It is enforced at one point in the rendering pipeline, so one that masks on the dashboard masks identically on the wall. Masking governs people columns only, so one ranking stores or sites keeps their real names.

Thirteen — ranked list, stat, table, chart, line, movers, gauge, status grid, share, streak, pace, scorecard, and calendar. Pie charts and charts over arbitrary columns are not available.

The board renders a "source unavailable" state instead of breaking or going blank, on every surface it was placed on. The admin Analytics tab lists every board in that state alongside what it was bound to and why the binding failed.

Two tiers. Contributors create, edit, duplicate, and preview boards; admins additionally hold app settings, archiving, signage publishing, and the public links that publish to the open web. Who sees a visualization inside MangoApps is set by an optional audience group; signage and embeds have no viewer at all, so one limited to an audience cannot be published there, and masking is what protects the ones that are.

Build a screen rotation — a named, ordered set of up to 20 visualizations with its own seconds-per-board setting — have an admin turn on its shared link, and paste that link into the panel's browser. Only visualizations that individually have external embed allowed appear in a public rotation, so a rotation is never a side door around that switch.

Yes, per visualization and off by default. An admin allowing external embed creates an unguessable link that renders it read-only with its masking applied and no login required. An optional allowlist restricts which sites may frame it, and rotating the link invalidates every one already shared.

A goal is a target value plus a direction — at least, or at most — with an optional warning threshold for a middle band. Values colour green, amber, or red with a progress bar, entries meeting the target get a Goal badge, and gauges draw the whole thing as an arc. It is display logic only; the underlying data is never filtered.

If its author switches the alert on — it is offered on stat, line, and gauge visualizations. It notifies when the value crosses its target and again when it recovers, reaching the person who added it, an optional group, and anyone watching it — on band changes only, so one that stays red does not re-notify. Separately, a Monday summary goes to everyone who watches a visualization — as a notification in the app, and by email too where they have an address — listing the ones they can open, watched ones first.

Yes — each visualization's history page exports its daily snapshot series to CSV over the window shown on screen, with windows of 7, 30, 90, or 365 days. A read-only REST API also returns boards, their current readings, and playlists; creating and editing boards still goes through the app.

Never a row of it. "Suggest with AI" drafts a leaderboard — chart type, entity and score columns, aggregate, and ordering — from the table's name and description, its column names and types, and whatever the author types in the box. It also never invents a numeric goal; a threshold only reaches the form if you typed that number yourself.