Is this dashboard showing old numbers?Now your viewers can tell at a glance.

Saved to your cloud

You publish the .twbx to a project on your Tableau Cloud site, like any workbook. The app's code rides inside the workbook (Tableau calls this a data app), so Tableau hosts it: it opens under your site's own URL, sign-in and project permissions. There is no extension URL to allowlist, viewers get no permission prompt, and there is no TableauOps server to trust. A new version is a new .twbx you republish. Your site admin does need data apps turned on (the site's Packages setting).

Getting it onto your site

1. Turn on data apps. A site admin enables the site's Packages setting once. Skip this if your site already runs data apps.
2. Download the workbook from the email: Freshness Badge.twbx.
3. Upload it to a project. In Tableau Cloud, open the project you want it in, choose New → Upload Workbook, and pick the file. Don't double-click it: data apps run only on Tableau Cloud for now, and Tableau Desktop can't open them yet.
4. Open the view. It runs on the bundled sample log, so you see fresh, late and failing before connecting anything.
5. Point it at Job Performance. Edit the workbook, connect Admin Insights → Job Performance, then Data → Replace Data Source. Save, and every data source on your site gets a badge: fresh, late or failing.
6. Optional: badge dashboards, not sources. Add a short workbook-to-source list (the template shows the shape) to the refreshes in one table, for example with a Tableau Prep flow, and each dashboard gets the badge of its stalest source.
7. Place it. Taller than about 220px it shows every badge, worst first. Shorter, it's one strip, and the gear in edit mode picks which one it watches.

Connected to your admin data

The badge reads the data source behind its own sheet, inside Tableau. Point that at Admin Insights, the project Tableau Cloud keeps for site admins: Job Performance supplies each refresh, its result and its error, and TS Events adds who opened which workbook. The badge maps their columns by name, so no renaming in the usual case.

Job Performance alone is enough: the badge learns each source's refresh rhythm from it and badges every source on its own. One thing Admin Insights doesn't record is which data sources each workbook uses, so for a badge per dashboard you add that as a short list, one row per workbook and source, in the same table. The badges move when Admin Insights refreshes, so they are as current as that data.

Honest note: we tested it on a field-for-field replica of Job Performance and TS Events built from a real site's activity log, not yet on Tableau's own Admin Insights. If a column doesn't line up, the badge names what's missing, and a reply to the delivery email gets it fixed.