Tableau WP Bridge plugins typically register a custom post type like tableau_dashboard or tableau_view for each embedded workbook, with the workbook URL, site name, view path, and refresh token stored in wp_postmeta. Sync history and refresh attempts are usually written to a log table such as wp_tableau_sync_log or to wp_options entries when the bridge is light-touch.

The default WordPress list table for tableau_dashboard shows title, author, and date. It does not surface the workbook ID, the embed mode, the last refresh timestamp, or which page on your site actually embeds the view. Finding stale dashboards or broken refresh tokens means opening each post or tailing the bridge's debug log.

SleekView reads the Tableau bridge custom post type plus the matching wp_postmeta rows and joins them with the sync log table. Workbook, view path, embed mode, last refresh status, last refresh time, and the embedding page all appear in one row. Edits route through the bridge's own REST handlers when present, falling back to safe update_post_meta writes with conflict detection.

Tableau dashboards embedded into WordPress sit in an awkward operational seam. The workbook lives in Tableau Server or Tableau Cloud where the data and refresh schedules are governed, but the embed config (which workbook, which view, which page, which mode) lives in WordPress as scattered custom posts and meta keys. Most bridge plugins ship a minimal admin that lists dashboards by title and date and not much else.

That works for a handful of embeds and falls apart at twenty or fifty. Analytics ops cannot tell at a glance which embeds are stale, who owns them, or which pages they appear on. Governance teams cannot audit which Tableau views are exposed outside the intranet without opening each post by hand.

SleekView treats the bridge's records as the structured data they actually are. The dashboard post, its meta, the latest sync log row, and the embedding page all become joinable columns. The result is a single audit grid that maps the WordPress side of the Tableau deployment, makes broken refreshes visible immediately, and lets the team enforce ownership and exposure rules without leaving the admin.