Skip to main content

​
Connection & Authentication

Connected Apps with Direct Trust is the recommended method for all environments. It uses OAuth-based authentication without requiring a user password and is the most secure and debuggable option.
For Connected Apps authentication, the user must have at minimum Site Admin Creator privileges. Site Admin Explorer may work in some environments but has caused connectivity issues in others. The user must have access to the Metadata API and REST APIs.
Yes. Prizm supports both deployment types. Create a separate connector for each deployment. For Tableau Cloud, ensure the HTTPS scheme is included in the host URL — Tableau Cloud does not support HTTP for Metadata API access.
Inspect the Tableau URL in your browser. The site name appears after /site/ in the URL path:
  • https://prod-uswest-b.online.tableau.com/#/site/staging/projects → site name: staging
  • http://techdata.io/#/site/AnalyticsTeam/projects → site name: AnalyticsTeam
Site name is case-sensitive and must match exactly. If your environment uses the Default Site, leave the Site Name field blank.
Personal Access Tokens must be manually rotated in Tableau (User Settings → Access Tokens) and updated in the Prizm connector settings. Tableau does not auto-refresh PATs. Connected Apps authentication is recommended to avoid manual rotation.

​
Asset Selection & Scoping

Yes. During setup, Prizm presents a list of all available workbooks in the configured site. Use checkboxes to select exactly which workbooks to bring into Prizm. You can add or remove workbooks at any time from the connector asset selection page.
Use the Sync action from the connector asset selection page. Sync detects workbooks that have been deleted in Tableau and automatically marks the corresponding assets as deprecated in Prizm. Deprecated assets are retained in the catalog for historical lineage and audit purposes.
Tableau Flows are captured in the data model (TableauFlow object) but full Flow observability is not currently in scope for the connector. Tableau Metrics (the native Tableau Metrics feature) are deprecated by Tableau and are not ingested by Prizm.
Create a separate connector for each site. Each connector has its own credentials, site name, workbook selection, and job schedules.

​
Lineage

Lineage is auto-inferred from the upstreamTables and upstreamColumns declared in the Tableau datasource metadata (via the Metadata API). Prizm stitches this with the warehouse-side lineage from Snowflake or Databricks to produce an end-to-end graph:Warehouse table → Published Data Source → Worksheet → DashboardColumn-level lineage (which warehouse column maps to which Tableau field) is also available where Tableau datasource fields declare upstream column references.
Yes. From the Lineage tab on any Tableau asset, you can manually map upstream or downstream assets by selecting the required asset names from the dropdown. Manual lineage mappings are preserved across catalog syncs.
The Catalog job runs immediately after the connector is saved. Lineage data is available within a few minutes for most environments. End-to-end stitching with warehouse-side lineage may take up to 24 hours due to batching.

​
Observability & Freshness

Prizm tracks the last_successful_refresh_time for each Tableau extract via the Extract Refresh Tasks API (REST). The freshness threshold is calculated dynamically:Expected Range = (expected refresh interval − last successful refresh time) ± 3 × average execution timeThis means the threshold automatically adjusts to your extract schedule. You can also set a manual threshold if you need a fixed SLA window.
The Operational/Refresh job (runs hourly) tracks: freshness delay, refresh success rate, consecutive failures, and p95 refresh duration. Only extract refresh tasks and related background jobs are monitored — permission jobs, subscription sends, and thumbnail generation are excluded.
Yes. Usage metrics (hits_last_14d, hits_last_30d, hits_last_90d, hits_last_365d) are collected daily. Workbooks with no views in 90+ days can be flagged for deprecation review. The usage-weighted health score also surfaces high-traffic workbooks with quality issues first.

​
Quality Propagation

When propagation is enabled, Prizm automatically links the quality state of upstream warehouse tables to the Tableau workbooks that consume them. When an alert fires or an issue is created on a warehouse table, the signal propagates downstream to every Tableau workbook that queries that table.Propagation is configured per signal (Alerts, Issues, Score) and can be set to Based on associated table or None.
Score propagation surfaces upstream table quality scores inside Prizm on the Tableau workbook asset page — visible to Prizm users.Data Quality Warnings push a warning directly into Tableau Server or Tableau Cloud, where it appears on the Tableau Data Source and overlays on views consuming it — visible to all Tableau users regardless of Prizm access. DQ Warnings require Tableau Enterprise or the Data Management add-on.
Check the following:
  1. Your Tableau license includes Data Quality Warnings (Tableau Enterprise, Tableau+, or Data Management add-on purchased before September 16, 2024)
  2. Tableau Catalog is enabled on your instance
  3. Warnings apply only to Tableau Data Sources — not to Workbooks or Views directly
  4. Warnings expire approximately 24 hours after being set — re-apply if needed
  5. The Prizm user has sufficient permissions to write DQ warnings to the Tableau site

​
Connector Lifecycle

Schedules can be overridden from the connector detail page.
Paused: Existing metadata, scores, and propagated signals are retained. No new data is collected until the connector is re-enabled.Deleted: Once approved through the deletion workflow, the connector and all associated metadata are permanently removed. This action cannot be undone.
Check the following:
  1. Confirm the workbook is selected in the connector’s asset selection list
  2. Verify the Tableau user has permission to see the workbook (Prizm respects Tableau permissions)
  3. Check that the Catalog job has completed at least one successful run — go to Settings → Sources → Logs
  4. If the workbook was recently published, trigger an on-demand Catalog sync
  5. If the issue persists, contact Prizm Support
For connection errors and authentication issues, see the Troubleshooting page. For definitions of terms used in this FAQ, see the Glossary.