Tableau - Parable

Sync workbooks, views, users, and jobs from Tableau Server or Tableau Cloud.

Overview
Setup Guide
Permissions
Troubleshooting

Personal Access Token (recommended)

Connect Parable to Tableau Server or Tableau Cloud with a Personal Access Token. Parable exchanges the PAT at /auth/signin for an X-Tableau-Auth session and discovers the site LUID automatically.

Content

Workbooks, views, data sources, projects, flows

Usage and users

Users, groups, jobs, subscriptions

Connected Apps (Direct Trust JWT)

Connect Parable to Tableau using a Connected App with Direct Trust. Parable mints a short-lived HS256 JWT and exchanges it at /auth/signin for an X-Tableau-Auth session. This is not browser OAuth (no authorize redirect).

Username and password (Tableau Server)

Connect Parable to Tableau Server with username and password. Parable exchanges credentials at /auth/signin for an X-Tableau-Auth session.

Warning: Not available on Tableau Cloud when MFA is enabled. Prefer Personal Access Token or Connected Apps.

Data streams

This Provider Plugin defines 18 data streams.

Stream	Description	Sync
`users`	Tableau site users	full
`groups`	Tableau site groups	full
`group_users`	Users that belong to a Tableau group	full
`projects`	Tableau projects	incremental
`workbooks`	Published Tableau workbooks	incremental
`views`	Tableau views/dashboards on a site	incremental
`custom_views`	Saved custom views	incremental
`datasources`	Published data sources	incremental
`datasource_connections`	Connection configs for a published data source	full
`jobs`	Background jobs on the site	incremental
`extract_refresh_tasks`	Scheduled extract refresh tasks	full
`flows`	Tableau Prep flows	incremental
`flow_tasks`	Scheduled flow run tasks	full
`flow_runs`	Historical Tableau Prep flow runs	incremental
`subscriptions`	Content subscriptions	full
`schedules`	Server schedules (Tableau Server only; not available on Tableau Cloud)	full
`workbook_views`	Views nested under a workbook (opt-in; site views is default)	full
`activity_events`	Tableau Cloud Manager / activity log events (opt-in; requires TCM host and admin access)	incremental

Personal Access Token (recommended)

What You’ll Need

Credential	What it is
Token Name	PAT identifier from My Account Settings
Token Secret	PAT secret value (shown once at creation)
Site Name	Tableau site content URL slug (from your site URL; blank for Default)
Base URL	Tableau Server/Cloud URL (e.g. `https://yourcompany.online.tableau.com`)

Info: These steps require Site Administrator, or a colleague who can create a PAT for you.

Personal Access Tokens enabled on your site
Site Administrator role (for full tap coverage)

Step 1: Access Account Settings

Sign in to Tableau Server/Cloud
Click your avatar → My Account Settings
Open Personal Access Tokens

Step 2: Create Personal Access Token

Enter a token name: Parable Integration
Click Create new token
Copy both Token name and Token secret

Warning: Copy the token secret now. Tableau shows it only once.

Step 3: Note your server details

Detail	Example
Base URL	`https://yourcompany.online.tableau.com` or `https://tableau.yourcompany.com`
Site Name	content URL slug from the site URL (empty for Default site)

Step 4: Enter values in Parable

Choose Personal Access Token
Enter Base URL, Site Name, Token Name, Token Secret
Click Save & test connection

Successful Save & test stores the site LUID from sign-in for subsequent syncs.

curl -X POST "https://YOUR_SERVER/api/3.29/auth/signin" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json" \
  -d '{
    "credentials": {
      "personalAccessTokenName": "YOUR_TOKEN_NAME",
      "personalAccessTokenSecret": "YOUR_TOKEN_SECRET",
      "site": {
        "contentUrl": "YOUR_SITE_CONTENT_URL"
      }
    }
  }'

The response includes credentials.token and credentials.site.id (site LUID). Use the LUID in later calls:

Test API (with session token)

curl -H "X-Tableau-Auth: YOUR_AUTH_TOKEN" \
  -H "Accept: application/json" \
  "https://YOUR_SERVER/api/3.29/sites/YOUR_SITE_LUID/users?pageSize=1"

Success: 200 OK with user data means credentials work.

Connected Apps (Direct Trust JWT)

What You’ll Need

Credential	What it is
Connected App Client ID	Client ID from Tableau Connected Apps (Direct Trust)
Secret ID	Secret key ID (`kid`) from the Connected App
Secret Value	Shared secret used to sign the JWT
Impersonate User	Tableau user email used as the JWT `sub` claim
Site Name	Site content URL slug (blank for the Default site)
Base URL	Tableau Server/Cloud URL (e.g. `https://yourcompany.online.tableau.com`)

Info: Requires a Tableau site administrator (or Cloud admin) to create the Connected App.

Connected Apps enabled on the site
A Tableau user email that Parable should act as (sub)
REST API scopes enabled on the Connected App for the methods you need

Step 1: Create a Connected App (Direct Trust)

Sign in to Tableau Server/Cloud as an admin
Open Settings → Connected Apps
Create a Direct Trust Connected App
Enable the app
Generate a secret and copy:
- Client ID
- Secret ID
- Secret value

Step 2: Note site and server details

Detail	Example
Base URL	`https://yourcompany.online.tableau.com`
Site Name	content URL slug from the site URL (or blank for Default)
Impersonate User	`admin@yourcompany.com`

Step 3: Enter values in Parable

Choose Connected Apps (Direct Trust JWT)
Enter Client ID, Secret ID, Secret value, Impersonate User, Site Name, Base URL
Optionally set scopes (space-separated). Defaults cover content/users/projects read scopes
Click Save & test connection

Successful Save & test means Parable signed in and listed users with the session token. Parable stores the site LUID from sign-in automatically.

Username and password (Tableau Server)

What You’ll Need

Credential	What it is
Username	Tableau Server username
Password	Tableau Server password
Site Name	Site content URL slug (blank for the Default site)
Base URL	Tableau Server URL

Tableau Server (not Cloud + MFA)
A user with Site Administrator (or sufficient role for the taps you enable)

Sign in to Tableau Server with the username/password you will use
Confirm MFA is not required for that account

Step 2: Note server details

Detail	Example
Base URL	`https://tableau.yourcompany.com`
Site Name	content URL slug (or blank for Default)

Step 3: Enter values in Parable

Choose Username and password (Tableau Server)
Enter Username, Password, Site Name, Base URL
Click Save & test connection

Activity Events

Developer identifier: activity_eventsActivity Events contain Tableau Cloud Manager / activity log events (opt-in; requires TCM host and admin access).

Enables: trace opted-in Tableau Cloud Manager events to the recorded actor, site, and event time.
Scope: Reads provider changes through GET /api/{apiVersion}/activity/events using the declared incremental request boundary. This opt-in endpoint requires a Tableau Cloud Manager host and administrator access.

Actor User ID

Developer identifier: activity_events.actorUserIdActor User ID carries the source identifier named Actor User ID for each activity event row. It is needed to resolve references that repeat the same provider identifier.

Enables: match activity event records to provider records that carry the same actor user ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies actorUserId as a record-level identifier on ActivityEvents. It identifies Tableau catalog relationships and does not establish effective access. Tableau identifiers and view metadata do not prove effective access.

Actor User Name

Developer identifier: activity_events.actorUserNameActor User Name carries the source person or account value named Actor User Name for each activity event row. It keeps the provider-reported person or account context attached to the record.

Enables: attribute the activity event record to the provider-reported actor represented by actor user name.
Interpretation: The provider supplies actorUserName as identity or attribution context on each activity event record. Names and contact values can change and are not stable identifiers unless the provider documents them as such.

Event Time

Developer identifier: activity_events.eventTimeEvent Time carries the source date or timestamp named Event Time for each activity event row. It anchors the named event or boundary on the record’s timeline.

Enables: place activity event records on a timeline by event time and select the records within an explicit reporting window.
Interpretation: The provider supplies eventTime per activity event record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.

Event Type

Developer identifier: activity_events.eventTypeEvent Type carries the source state or classification named Event Type for each activity event row. It preserves the provider’s current classification of this record.

Enables: separate activity event records by the exact provider-reported event type value when describing their recorded state.
Interpretation: The provider supplies eventType per activity event record using its own state vocabulary; unknown and missing values must remain distinct.

Developer identifier: activity_events.idID is the declared record key for each activity event row. It supplies the declared record identity used when repeated ingestions represent the same source row.

Enables: recognize repeated ingestions of the same activity event source row before constructing its represented state.
Interpretation: The provider supplies id at one value per activity event record, and x-transformDedupKey explicitly marks it as the record key. Tableau identifiers and view metadata do not prove effective access.

Site LUID

Developer identifier: activity_events.siteLuidSite LUID carries the source identifier named Site LUID for each activity event row. It is needed to resolve references that repeat the same provider identifier.

Enables: match activity event records to provider records that carry the same site LUID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies siteLuid as a record-level identifier on ActivityEvents. It identifies Tableau catalog relationships and does not establish effective access. Tableau identifiers and view metadata do not prove effective access.

Custom Views

Developer identifier: custom_viewsCustom Views contain saved custom views.

Enables: catalog saved custom views with owner and source-view references.
Scope: Reads provider changes through GET /api/{apiVersion}/sites/{siteId}/customviews using the declared incremental request boundary. Results are limited to objects returned for the authenticated Tableau site; identifiers and view metadata do not establish effective access.

Created At

Developer identifier: custom_views.createdAtCreated At carries the source date or timestamp named Created At for each custom view row. It anchors the named event or boundary on the record’s timeline.

Enables: place custom view records on a timeline by created at and select the records within an explicit reporting window.
Interpretation: The provider supplies createdAt per custom view record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported. Tableau identifiers and view metadata do not prove effective access.

Developer identifier: custom_views.idID identifies Tableau LUID. It supplies the declared record identity used when repeated ingestions represent the same source row.

Enables: recognize repeated ingestions of the same custom view source row before constructing its represented state.
Interpretation: The provider supplies id at one value per custom view record, and x-transformDedupKey explicitly marks it as the record key. Tableau identifiers and view metadata do not prove effective access.

Last Accessed At

Developer identifier: custom_views.lastAccessedAtLast Accessed At carries the source date or timestamp named Last Accessed At for each custom view row. It anchors the named event or boundary on the record’s timeline.

Enables: place custom view records on a timeline by last accessed at and select the records within an explicit reporting window.
Interpretation: The provider supplies lastAccessedAt per custom view record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported. Tableau identifiers and view metadata do not prove effective access.

Name

Developer identifier: custom_views.nameName carries the source-authored value named Name for each custom view row. It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact name value attached to each custom view record.
Interpretation: The provider supplies name at custom view granularity in the format stated by its description; omitted or redacted content remains unknown. Tableau identifiers and view metadata do not prove effective access.

Owner ID

Developer identifier: custom_views.owner_idOwner ID carries the source identifier named Owner ID for each custom view row. It is needed to resolve references that repeat the same provider identifier.

Enables: match custom view records to provider records that carry the same owner ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies owner_id as a record-level identifier on CustomViews. It identifies Tableau catalog relationships and does not establish effective access. Tableau identifiers and view metadata do not prove effective access.

Owner Name

Developer identifier: custom_views.owner_nameOwner Name carries the source person or account value named Owner Name for each custom view row. It keeps the provider-reported person or account context attached to the record.

Enables: attribute the custom view record to the provider-reported actor represented by owner name.
Interpretation: The provider supplies owner_name as identity or attribution context on each custom view record. Names and contact values can change and are not stable identifiers unless the provider documents them as such. Tableau identifiers and view metadata do not prove effective access.

Shared

Developer identifier: custom_views.sharedShared carries the source true-or-false flag named Shared for each custom view row. It preserves the provider-reported yes-or-no condition for this record.

Enables: select custom view records for which the provider reports shared as true or false.
Interpretation: The provider supplies shared as a boolean per custom view record; false and missing are distinct when the field is optional. Tableau identifiers and view metadata do not prove effective access.

Updated At

Developer identifier: custom_views.updatedAtUpdated At carries the source date or timestamp named Updated At for each custom view row. It anchors the named event or boundary on the record’s timeline.

Enables: place custom view records on a timeline by updated at and select the records within an explicit reporting window.
Interpretation: The provider supplies updatedAt per custom view record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported. Tableau identifiers and view metadata do not prove effective access.

View ID

Developer identifier: custom_views.view_idView ID carries the source identifier named View ID for each custom view row. It is needed to resolve references that repeat the same provider identifier.

Enables: match custom view records to provider records that carry the same view ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies view_id as a record-level identifier on CustomViews. It identifies Tableau catalog relationships and does not establish effective access. Tableau identifiers and view metadata do not prove effective access.

View Name

Developer identifier: custom_views.view_nameView Name carries the source-authored value named View Name for each custom view row. It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact view name value attached to each custom view record.
Interpretation: The provider supplies view_name at custom view granularity in the format stated by its description; omitted or redacted content remains unknown. Tableau identifiers and view metadata do not prove effective access.

Workbook ID

Developer identifier: custom_views.workbook_idWorkbook ID carries the source identifier named Workbook ID for each custom view row. It is needed to resolve references that repeat the same provider identifier.

Enables: match custom view records to provider records that carry the same workbook ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies workbook_id as a record-level identifier on CustomViews. It identifies Tableau catalog relationships and does not establish effective access. Tableau identifiers and view metadata do not prove effective access.

Datasource Connections

Developer identifier: datasource_connectionsDatasource Connections contain connection configs for a published data source.

Enables: inspect connection configuration returned for a published data source.
Scope: Reads the declared collection through GET /api/{apiVersion}/sites/{siteId}/datasources/{datasource_id}/connections as a full snapshot. Results are limited to objects returned for the authenticated Tableau site; identifiers and view metadata do not establish effective access.

Datasource ID

Developer identifier: datasource_connections.datasource_idDatasource ID identifies parent datasource LUID from fan-out. It is needed to resolve references that repeat the same provider identifier.

Enables: match datasource connection records to provider records that carry the same datasource ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies datasource_id as a record-level identifier on DatasourceConnections. It identifies Tableau catalog relationships and does not establish effective access. Tableau identifiers and view metadata do not prove effective access.

Developer identifier: datasource_connections.idID is the declared record key for each datasource connection row. It supplies the declared record identity used when repeated ingestions represent the same source row.

Enables: recognize repeated ingestions of the same datasource connection source row before constructing its represented state.
Interpretation: The provider supplies id at one value per datasource connection record, and x-transformDedupKey explicitly marks it as the record key. Tableau identifiers and view metadata do not prove effective access.

Server Address

Developer identifier: datasource_connections.serverAddressServer Address carries the source configuration value named Server Address for each datasource connection row. It preserves the configuration or technical value needed to explain how the provider object is defined.

Enables: inspect the exact server address when validating the configuration or technical definition of a datasource connection record.
Interpretation: The provider supplies serverAddress as configuration or technical metadata on DatasourceConnections; consumers must preserve the exact syntax and documented vocabulary.

Server Port

Developer identifier: datasource_connections.serverPortServer Port carries the source configuration value named Server Port for each datasource connection row. It preserves the configuration or technical value needed to explain how the provider object is defined.

Enables: inspect the exact server port when validating the configuration or technical definition of a datasource connection record.
Interpretation: The provider supplies serverPort as configuration or technical metadata on DatasourceConnections; consumers must preserve the exact syntax and documented vocabulary.

Type

Developer identifier: datasource_connections.typeType carries the source state or classification named Type for each datasource connection row. It preserves the provider’s current classification of this record.

Enables: separate datasource connection records by the exact provider-reported type value when describing their recorded state.
Interpretation: The provider supplies type per datasource connection record using its own state vocabulary; unknown and missing values must remain distinct.

User Name

Developer identifier: datasource_connections.userNameUser Name records connection login username (not email). It keeps the provider-reported person or account context attached to the record.

Enables: attribute the datasource connection record to the provider-reported actor represented by user name.
Interpretation: The provider supplies userName as identity or attribution context on each datasource connection record. Names and contact values can change and are not stable identifiers unless the provider documents them as such.

Datasources

Developer identifier: datasourcesDatasources contain published data sources.

Enables: catalog published data sources with their project, owner, and extract metadata.
Scope: Reads provider changes through GET /api/{apiVersion}/sites/{siteId}/datasources using the declared incremental request boundary. Results are limited to objects returned for the authenticated Tableau site; identifiers and view metadata do not establish effective access.

Certification Note

Developer identifier: datasources.certificationNoteCertification Note carries the source-authored value named Certification Note for each datasource row. It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact certification note value attached to each datasource record.
Interpretation: The provider supplies certificationNote at datasource granularity in the format stated by its description; omitted or redacted content remains unknown.

Content URL

Developer identifier: datasources.contentUrlContent URL carries the provider-reported content url for each datasource record. It retains the exact provider location for the referenced resource.

Enables: open or trace the exact provider resource referenced by content URL on a datasource record.
Interpretation: The provider supplies contentUrl as a URL or resource locator on each datasource record. It identifies a Tableau catalog location but does not prove who can open it.

Created At

Developer identifier: datasources.createdAtCreated At carries the source date or timestamp named Created At for each datasource row. It anchors the named event or boundary on the record’s timeline.

Enables: place datasource records on a timeline by created at and select the records within an explicit reporting window.
Interpretation: The provider supplies createdAt per datasource record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.

Description

Developer identifier: datasources.descriptionDescription carries the source-authored value named Description for each datasource row. It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact description value attached to each datasource record.
Interpretation: The provider supplies description at datasource granularity in the format stated by its description; omitted or redacted content remains unknown.

Encrypt Extracts

Developer identifier: datasources.encryptExtractsEncrypt Extracts carries the source true-or-false flag named Encrypt Extracts for each datasource row. It preserves the provider-reported yes-or-no condition for this record.

Enables: select datasource records for which the provider reports encrypt extracts as true or false.
Interpretation: The provider supplies encryptExtracts as a boolean per datasource record; false and missing are distinct when the field is optional.

Has Extracts

Developer identifier: datasources.hasExtractsHas Extracts carries the source true-or-false flag named Has Extracts for each datasource row. It preserves the provider-reported yes-or-no condition for this record.

Enables: select datasource records for which the provider reports has extracts as true or false.
Interpretation: The provider supplies hasExtracts as a boolean per datasource record; false and missing are distinct when the field is optional.

Developer identifier: datasources.idID identifies Tableau LUID. It supplies the declared record identity used when repeated ingestions represent the same source row.

Enables: recognize repeated ingestions of the same datasource source row before constructing its represented state.
Interpretation: The provider supplies id at one value per datasource record, and x-transformDedupKey explicitly marks it as the record key. Tableau identifiers and view metadata do not prove effective access.

Is Certified

Developer identifier: datasources.isCertifiedIs Certified carries the source true-or-false flag named Is Certified for each datasource row. It preserves the provider-reported yes-or-no condition for this record.

Enables: select datasource records for which the provider reports is certified as true or false.
Interpretation: The provider supplies isCertified as a boolean per datasource record; false and missing are distinct when the field is optional.

Name

Developer identifier: datasources.nameName carries the source-authored value named Name for each datasource row. It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact name value attached to each datasource record.
Interpretation: The provider supplies name at datasource granularity in the format stated by its description; omitted or redacted content remains unknown.

Owner ID

Developer identifier: datasources.owner_idOwner ID carries the source identifier named Owner ID for each datasource row. It is needed to resolve references that repeat the same provider identifier.

Enables: match datasource records to provider records that carry the same owner ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies owner_id as a record-level identifier on Datasources. It identifies Tableau catalog relationships and does not establish effective access. Tableau identifiers and view metadata do not prove effective access.

Owner Name

Developer identifier: datasources.owner_nameOwner Name carries the source person or account value named Owner Name for each datasource row. It keeps the provider-reported person or account context attached to the record.

Enables: attribute the datasource record to the provider-reported actor represented by owner name.
Interpretation: The provider supplies owner_name as identity or attribution context on each datasource record. Names and contact values can change and are not stable identifiers unless the provider documents them as such.

Project ID

Developer identifier: datasources.project_idProject ID carries the source identifier named Project ID for each datasource row. It is needed to resolve references that repeat the same provider identifier.

Enables: match datasource records to provider records that carry the same project ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies project_id as a record-level identifier on Datasources. It identifies Tableau catalog relationships and does not establish effective access. Tableau identifiers and view metadata do not prove effective access.

Project Name

Developer identifier: datasources.project_nameProject Name carries the source-authored value named Project Name for each datasource row. It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact project name value attached to each datasource record.
Interpretation: The provider supplies project_name at datasource granularity in the format stated by its description; omitted or redacted content remains unknown.

Type

Developer identifier: datasources.typeType carries the source state or classification named Type for each datasource row. It preserves the provider’s current classification of this record.

Enables: separate datasource records by the exact provider-reported type value when describing their recorded state.
Interpretation: The provider supplies type per datasource record using its own state vocabulary; unknown and missing values must remain distinct.

Updated At

Developer identifier: datasources.updatedAtUpdated At carries the source date or timestamp named Updated At for each datasource row. It anchors the named event or boundary on the record’s timeline.

Enables: place datasource records on a timeline by updated at and select the records within an explicit reporting window.
Interpretation: The provider supplies updatedAt per datasource record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.

Use Remote Query Agent

Developer identifier: datasources.useRemoteQueryAgentUse Remote Query Agent carries the source true-or-false flag named Use Remote Query Agent for each datasource row. It preserves the provider-reported yes-or-no condition for this record.

Enables: select datasource records for which the provider reports use remote query agent as true or false.
Interpretation: The provider supplies useRemoteQueryAgent as a boolean per datasource record; false and missing are distinct when the field is optional.

Extract Refresh Tasks

Developer identifier: extract_refresh_tasksExtract Refresh Tasks contain scheduled extract refresh tasks.

Enables: review scheduled extract refresh configuration and consecutive failure counts.
Scope: Reads the declared collection through GET /api/{apiVersion}/sites/{siteId}/tasks/extractRefreshes as a full snapshot. Results are limited to objects returned for the authenticated Tableau site; identifiers and view metadata do not establish effective access.

Consecutive Failed Count

Developer identifier: extract_refresh_tasks.consecutiveFailedCountConsecutive Failed Count carries the source measure named Consecutive Failed Count for each extract refresh task row. It preserves the stated measure at this record’s granularity.

Enables: measure the provider-reported consecutive failed count for each extract refresh task record.
Interpretation: The provider supplies consecutiveFailedCount at extract refresh task granularity as a count at one value per record; zero and missing are not interchangeable.

Datasource ID

Developer identifier: extract_refresh_tasks.datasource_idDatasource ID carries the source identifier named Datasource ID for each extract refresh task row. It is needed to resolve references that repeat the same provider identifier.

Enables: match extract refresh task records to provider records that carry the same datasource ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies datasource_id as a record-level identifier on ExtractRefreshTasks. It identifies Tableau catalog relationships and does not establish effective access. Tableau identifiers and view metadata do not prove effective access.

Datasource Name

Developer identifier: extract_refresh_tasks.datasource_nameDatasource Name carries the source-authored value named Datasource Name for each extract refresh task row. It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact datasource name value attached to each extract refresh task record.
Interpretation: The provider supplies datasource_name at extract refresh task granularity in the format stated by its description; omitted or redacted content remains unknown.

Extract Refresh

Developer identifier: extract_refresh_tasks.extractRefreshExtract Refresh records nested extractRefresh payload from Tableau tasks.task envelope. It retains configured attributes whose keys or shape are not fixed by this base schema.

Enables: interpret extract refresh according to the provider and Workspace configuration that produced each extract refresh task record.
Interpretation: Keys and value shapes within extractRefresh can vary with provider and customer configuration; consumers must inspect the observed Workspace schema rather than assume a fixed contract.

Developer identifier: extract_refresh_tasks.idID identifies prefer extractRefresh.id when nested. It supplies the declared record identity used when repeated ingestions represent the same source row.

Enables: recognize repeated ingestions of the same extract refresh task source row before constructing its represented state.
Interpretation: The provider supplies id at one value per extract refresh task record, and x-transformDedupKey explicitly marks it as the record key. Tableau identifiers and view metadata do not prove effective access.

Priority

Developer identifier: extract_refresh_tasks.priorityPriority carries the source state or classification named Priority for each extract refresh task row. It preserves the provider’s current classification of this record.

Enables: separate extract refresh task records by the exact provider-reported priority value when describing their recorded state.
Interpretation: The provider supplies priority per extract refresh task record using its own state vocabulary; unknown and missing values must remain distinct.

Schedule Frequency

Developer identifier: extract_refresh_tasks.schedule_frequencySchedule Frequency carries the source period or schedule value named Schedule Frequency for each extract refresh task row. It preserves the provider-defined period or schedule cadence for this record.

Enables: group extract refresh task records by the provider-defined schedule frequency period or schedule.
Interpretation: The provider supplies schedule_frequency per extract refresh task record using its own period or schedule vocabulary; it is not an elapsed-duration measurement.

Schedule ID

Developer identifier: extract_refresh_tasks.schedule_idSchedule ID carries the source identifier named Schedule ID for each extract refresh task row. It is needed to resolve references that repeat the same provider identifier.

Enables: match extract refresh task records to provider records that carry the same schedule ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies schedule_id as a record-level identifier on ExtractRefreshTasks. It identifies Tableau catalog relationships and does not establish effective access. Tableau identifiers and view metadata do not prove effective access.

Schedule Name

Developer identifier: extract_refresh_tasks.schedule_nameSchedule Name carries the source-authored value named Schedule Name for each extract refresh task row. It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact schedule name value attached to each extract refresh task record.
Interpretation: The provider supplies schedule_name at extract refresh task granularity in the format stated by its description; omitted or redacted content remains unknown.

Schedule Next Run At

Developer identifier: extract_refresh_tasks.schedule_nextRunAtSchedule Next Run At carries the source date or timestamp named Schedule Next Run At for each extract refresh task row. It anchors the named event or boundary on the record’s timeline.

Enables: place extract refresh task records on a timeline by schedule next run at and select the records within an explicit reporting window.
Interpretation: The provider supplies schedule_nextRunAt per extract refresh task record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.

Type

Developer identifier: extract_refresh_tasks.typeType carries the source state or classification named Type for each extract refresh task row. It preserves the provider’s current classification of this record.

Enables: separate extract refresh task records by the exact provider-reported type value when describing their recorded state.
Interpretation: The provider supplies type per extract refresh task record using its own state vocabulary; unknown and missing values must remain distinct.

Workbook ID

Developer identifier: extract_refresh_tasks.workbook_idWorkbook ID carries the source identifier named Workbook ID for each extract refresh task row. It is needed to resolve references that repeat the same provider identifier.

Enables: match extract refresh task records to provider records that carry the same workbook ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies workbook_id as a record-level identifier on ExtractRefreshTasks. It identifies Tableau catalog relationships and does not establish effective access. Tableau identifiers and view metadata do not prove effective access.

Workbook Name

Developer identifier: extract_refresh_tasks.workbook_nameWorkbook Name carries the source-authored value named Workbook Name for each extract refresh task row. It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact workbook name value attached to each extract refresh task record.
Interpretation: The provider supplies workbook_name at extract refresh task granularity in the format stated by its description; omitted or redacted content remains unknown.

Flow Runs

Developer identifier: flow_runsFlow Runs contain historical Tableau Prep flow runs.

Enables: track historical Tableau Prep runs by status, progress, and timestamps.
Scope: Reads provider changes through GET /api/{apiVersion}/sites/{siteId}/flows/runs using the declared incremental request boundary. Results are limited to objects returned for the authenticated Tableau site; identifiers and view metadata do not establish effective access.

Background Job ID

Developer identifier: flow_runs.backgroundJobIdBackground Job ID carries the source identifier named Background Job ID for each flow run row. It is needed to resolve references that repeat the same provider identifier.

Enables: match flow run records to provider records that carry the same background job ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies backgroundJobId as a record-level identifier on FlowRuns. It identifies Tableau catalog relationships and does not establish effective access. Tableau identifiers and view metadata do not prove effective access.

Completed At

Developer identifier: flow_runs.completedAtCompleted At carries the source state or classification named Completed At for each flow run row. It preserves the provider’s current classification of this record.

Enables: separate flow run records by the exact provider-reported completed at value when describing their recorded state.
Interpretation: The provider supplies completedAt per flow run record using its own state vocabulary; unknown and missing values must remain distinct.

Flow ID

Developer identifier: flow_runs.flow_idFlow ID carries the source identifier named Flow ID for each flow run row. It is needed to resolve references that repeat the same provider identifier.

Enables: match flow run records to provider records that carry the same flow ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies flow_id as a record-level identifier on FlowRuns. It identifies Tableau catalog relationships and does not establish effective access. Tableau identifiers and view metadata do not prove effective access.

Developer identifier: flow_runs.idID is the declared record key for each flow run row. It supplies the declared record identity used when repeated ingestions represent the same source row.

Enables: recognize repeated ingestions of the same flow run source row before constructing its represented state.
Interpretation: The provider supplies id at one value per flow run record, and x-transformDedupKey explicitly marks it as the record key. Tableau identifiers and view metadata do not prove effective access.

Progress

Developer identifier: flow_runs.progressProgress records Tableau’s numeric progress value for the flow run. It preserves the execution-state value returned by the provider.

Enables: distinguish flow runs at different stages of execution after applying the scale used by the source export.
Interpretation: The provider supplies progress as an integer but this schema does not declare its range or unit; zero and missing are not interchangeable.

Started At

Developer identifier: flow_runs.startedAtStarted At carries the source date or timestamp named Started At for each flow run row. It anchors the named event or boundary on the record’s timeline.

Enables: place flow run records on a timeline by started at and select the records within an explicit reporting window.
Interpretation: The provider supplies startedAt per flow run record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.

Status

Developer identifier: flow_runs.statusStatus carries the source state or classification named Status for each flow run row. It preserves the provider’s current classification of this record.

Enables: separate flow run records by the exact provider-reported status value when describing their recorded state.
Interpretation: The provider supplies status per flow run record using its own state vocabulary; unknown and missing values must remain distinct.

Flow Tasks

Developer identifier: flow_tasksFlow Tasks contain scheduled flow run tasks.

Enables: review scheduled Tableau Prep flow task configuration.
Scope: Reads the declared collection through GET /api/{apiVersion}/sites/{siteId}/tasks/flows as a full snapshot. Results are limited to objects returned for the authenticated Tableau site; identifiers and view metadata do not establish effective access.

Consecutive Failed Count

Developer identifier: flow_tasks.consecutiveFailedCountConsecutive Failed Count carries the source measure named Consecutive Failed Count for each flow task row. It preserves the stated measure at this record’s granularity.

Enables: measure the provider-reported consecutive failed count for each flow task record.
Interpretation: The provider supplies consecutiveFailedCount at flow task granularity as a count at one value per record; zero and missing are not interchangeable.

Flow ID

Developer identifier: flow_tasks.flow_idFlow ID carries the source identifier named Flow ID for each flow task row. It is needed to resolve references that repeat the same provider identifier.

Enables: match flow task records to provider records that carry the same flow ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies flow_id as a record-level identifier on FlowTasks. It identifies Tableau catalog relationships and does not establish effective access. Tableau identifiers and view metadata do not prove effective access.

Flow Name

Developer identifier: flow_tasks.flow_nameFlow Name carries the source-authored value named Flow Name for each flow task row. It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact flow name value attached to each flow task record.
Interpretation: The provider supplies flow_name at flow task granularity in the format stated by its description; omitted or redacted content remains unknown.

Flow Run

Developer identifier: flow_tasks.flowRunFlow Run records nested flowRun payload when present on tasks.task. It retains configured attributes whose keys or shape are not fixed by this base schema.

Enables: interpret flow run according to the provider and Workspace configuration that produced each flow task record.
Interpretation: Keys and value shapes within flowRun can vary with provider and customer configuration; consumers must inspect the observed Workspace schema rather than assume a fixed contract.

Developer identifier: flow_tasks.idID is the declared record key for each flow task row. It supplies the declared record identity used when repeated ingestions represent the same source row.

Enables: recognize repeated ingestions of the same flow task source row before constructing its represented state.
Interpretation: The provider supplies id at one value per flow task record, and x-transformDedupKey explicitly marks it as the record key. Tableau identifiers and view metadata do not prove effective access.

Priority

Developer identifier: flow_tasks.priorityPriority carries the source state or classification named Priority for each flow task row. It preserves the provider’s current classification of this record.

Enables: separate flow task records by the exact provider-reported priority value when describing their recorded state.
Interpretation: The provider supplies priority per flow task record using its own state vocabulary; unknown and missing values must remain distinct.

Schedule Frequency

Developer identifier: flow_tasks.schedule_frequencySchedule Frequency carries the source period or schedule value named Schedule Frequency for each flow task row. It preserves the provider-defined period or schedule cadence for this record.

Enables: group flow task records by the provider-defined schedule frequency period or schedule.
Interpretation: The provider supplies schedule_frequency per flow task record using its own period or schedule vocabulary; it is not an elapsed-duration measurement.

Schedule ID

Developer identifier: flow_tasks.schedule_idSchedule ID carries the source identifier named Schedule ID for each flow task row. It is needed to resolve references that repeat the same provider identifier.

Enables: match flow task records to provider records that carry the same schedule ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies schedule_id as a record-level identifier on FlowTasks. It identifies Tableau catalog relationships and does not establish effective access. Tableau identifiers and view metadata do not prove effective access.

Schedule Name

Developer identifier: flow_tasks.schedule_nameSchedule Name carries the source-authored value named Schedule Name for each flow task row. It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact schedule name value attached to each flow task record.
Interpretation: The provider supplies schedule_name at flow task granularity in the format stated by its description; omitted or redacted content remains unknown.

Type

Developer identifier: flow_tasks.typeType carries the source state or classification named Type for each flow task row. It preserves the provider’s current classification of this record.

Enables: separate flow task records by the exact provider-reported type value when describing their recorded state.
Interpretation: The provider supplies type per flow task record using its own state vocabulary; unknown and missing values must remain distinct.

Flows

Developer identifier: flowsFlows contain Tableau Prep flows.

Enables: catalog Tableau Prep flows by project and owner.
Scope: Reads provider changes through GET /api/{apiVersion}/sites/{siteId}/flows using the declared incremental request boundary. Results are limited to objects returned for the authenticated Tableau site; identifiers and view metadata do not establish effective access.

Created At

Developer identifier: flows.createdAtCreated At carries the source date or timestamp named Created At for each flow row. It anchors the named event or boundary on the record’s timeline.

Enables: place flow records on a timeline by created at and select the records within an explicit reporting window.
Interpretation: The provider supplies createdAt per flow record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.

Description

Developer identifier: flows.descriptionDescription carries the source-authored value named Description for each flow row. It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact description value attached to each flow record.
Interpretation: The provider supplies description at flow granularity in the format stated by its description; omitted or redacted content remains unknown.

Developer identifier: flows.idID identifies Tableau LUID. It supplies the declared record identity used when repeated ingestions represent the same source row.

Enables: recognize repeated ingestions of the same flow source row before constructing its represented state.
Interpretation: The provider supplies id at one value per flow record, and x-transformDedupKey explicitly marks it as the record key. Tableau identifiers and view metadata do not prove effective access.

Name

Developer identifier: flows.nameName carries the source-authored value named Name for each flow row. It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact name value attached to each flow record.
Interpretation: The provider supplies name at flow granularity in the format stated by its description; omitted or redacted content remains unknown.

Owner ID

Developer identifier: flows.owner_idOwner ID carries the source identifier named Owner ID for each flow row. It is needed to resolve references that repeat the same provider identifier.

Enables: match flow records to provider records that carry the same owner ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies owner_id as a record-level identifier on Flows. It identifies Tableau catalog relationships and does not establish effective access. Tableau identifiers and view metadata do not prove effective access.

Owner Name

Developer identifier: flows.owner_nameOwner Name carries the source person or account value named Owner Name for each flow row. It keeps the provider-reported person or account context attached to the record.

Enables: attribute the flow record to the provider-reported actor represented by owner name.
Interpretation: The provider supplies owner_name as identity or attribution context on each flow record. Names and contact values can change and are not stable identifiers unless the provider documents them as such.

Project ID

Developer identifier: flows.project_idProject ID carries the source identifier named Project ID for each flow row. It is needed to resolve references that repeat the same provider identifier.

Enables: match flow records to provider records that carry the same project ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies project_id as a record-level identifier on Flows. It identifies Tableau catalog relationships and does not establish effective access. Tableau identifiers and view metadata do not prove effective access.

Project Name

Developer identifier: flows.project_nameProject Name carries the source-authored value named Project Name for each flow row. It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact project name value attached to each flow record.
Interpretation: The provider supplies project_name at flow granularity in the format stated by its description; omitted or redacted content remains unknown.

Updated At

Developer identifier: flows.updatedAtUpdated At carries the source date or timestamp named Updated At for each flow row. It anchors the named event or boundary on the record’s timeline.

Enables: place flow records on a timeline by updated at and select the records within an explicit reporting window.
Interpretation: The provider supplies updatedAt per flow record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.

Group Users

Developer identifier: group_usersGroup Users contain users that belong to a Tableau group.

Enables: map site accounts to a specific Tableau group.
Scope: Reads the declared collection through GET /api/{apiVersion}/sites/{siteId}/groups/{group_id}/users as a full snapshot. Results are limited to objects returned for the authenticated Tableau site; identifiers and view metadata do not establish effective access.

Auth Setting

Developer identifier: group_users.authSettingAuth Setting carries the source access or role value named Auth Setting for each group user row. It documents the access-related value reported for this object or membership.

Enables: describe the provider-reported auth setting attached to each group user record.
Interpretation: The provider supplies authSetting at group user granularity. For Tableau, this metadata does not prove effective access.

Group ID

Developer identifier: group_users.group_idGroup ID identifies parent group LUID from fan-out. It is needed to resolve references that repeat the same provider identifier.

Enables: match group user records to provider records that carry the same group ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies group_id as a record-level identifier on GroupUsers. It identifies Tableau catalog relationships and does not establish effective access. Tableau identifiers and view metadata do not prove effective access.

Developer identifier: group_users.idID identifies Tableau LUID. It supplies the declared record identity used when repeated ingestions represent the same source row.

Enables: recognize repeated ingestions of the same group user source row before constructing its represented state.
Interpretation: The provider supplies id at one value per group user record, and x-transformDedupKey explicitly marks it as the record key. Tableau identifiers and view metadata do not prove effective access.

Last Login

Developer identifier: group_users.lastLoginLast Login carries the source date or timestamp named Last Login for each group user row. It anchors the named event or boundary on the record’s timeline.

Enables: place group user records on a timeline by last login and select the records within an explicit reporting window.
Interpretation: The provider supplies lastLogin per group user record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.

Name

Developer identifier: group_users.nameName carries the source-authored value named Name for each group user row. It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact name value attached to each group user record.
Interpretation: The provider supplies name at group user granularity in the format stated by its description; omitted or redacted content remains unknown.

Site Role

Developer identifier: group_users.siteRoleSite Role carries the source access or role value named Site Role for each group user row. It documents the access-related value reported for this object or membership.

Enables: describe the provider-reported site role attached to each group user record.
Interpretation: The provider supplies siteRole at group user granularity. For Tableau, this metadata does not prove effective access.

Groups

Developer identifier: groupsGroups contain Tableau site groups.

Enables: catalog groups defined on the configured Tableau site.
Scope: Reads the declared collection through GET /api/{apiVersion}/sites/{siteId}/groups as a full snapshot. Results are limited to objects returned for the authenticated Tableau site; identifiers and view metadata do not establish effective access.

Domain Name

Developer identifier: groups.domain_nameDomain Name carries the source-authored value named Domain Name for each group row. It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact domain name value attached to each group record.
Interpretation: The provider supplies domain_name at group granularity in the format stated by its description; omitted or redacted content remains unknown.

Developer identifier: groups.idID identifies Tableau LUID. It supplies the declared record identity used when repeated ingestions represent the same source row.

Enables: recognize repeated ingestions of the same group source row before constructing its represented state.
Interpretation: The provider supplies id at one value per group record, and x-transformDedupKey explicitly marks it as the record key. Tableau identifiers and view metadata do not prove effective access.

Import Domain Name

Developer identifier: groups.import_domainNameImport Domain Name carries the source-authored value named Import Domain Name for each group row. It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact import domain name value attached to each group record.
Interpretation: The provider supplies import_domainName at group granularity in the format stated by its description; omitted or redacted content remains unknown.

Import Grant License Mode

Developer identifier: groups.import_grantLicenseModeImport Grant License Mode carries the source access or role value named Import Grant License Mode for each group row. It documents the access-related value reported for this object or membership.

Enables: describe the provider-reported import grant license mode attached to each group record.
Interpretation: The provider supplies import_grantLicenseMode at group granularity. For Tableau, this metadata does not prove effective access.

Import Site Role

Developer identifier: groups.import_siteRoleImport Site Role carries the source access or role value named Import Site Role for each group row. It documents the access-related value reported for this object or membership.

Enables: describe the provider-reported import site role attached to each group record.
Interpretation: The provider supplies import_siteRole at group granularity. For Tableau, this metadata does not prove effective access.

Name

Developer identifier: groups.nameName carries the source-authored value named Name for each group row. It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact name value attached to each group record.
Interpretation: The provider supplies name at group granularity in the format stated by its description; omitted or redacted content remains unknown.

Jobs

Developer identifier: jobsJobs contain background jobs on the site.

Enables: track background jobs by provider-reported type, state, progress, and timestamps.
Scope: Reads provider changes through GET /api/{apiVersion}/sites/{siteId}/jobs using the declared incremental request boundary. Results are limited to objects returned for the authenticated Tableau site; identifiers and view metadata do not establish effective access.

Completed At

Developer identifier: jobs.completedAtCompleted At carries the source state or classification named Completed At for each job row. It preserves the provider’s current classification of this record.

Enables: separate job records by the exact provider-reported completed at value when describing their recorded state.
Interpretation: The provider supplies completedAt per job record using its own state vocabulary; unknown and missing values must remain distinct.

Created At

Developer identifier: jobs.createdAtCreated At carries the source date or timestamp named Created At for each job row. It anchors the named event or boundary on the record’s timeline.

Enables: place job records on a timeline by created at and select the records within an explicit reporting window.
Interpretation: The provider supplies createdAt per job record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.

Datasource ID

Developer identifier: jobs.datasource_idDatasource ID carries the source identifier named Datasource ID for each job row. It is needed to resolve references that repeat the same provider identifier.

Enables: match job records to provider records that carry the same datasource ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies datasource_id as a record-level identifier on Jobs. It identifies Tableau catalog relationships and does not establish effective access. Tableau identifiers and view metadata do not prove effective access.

Extract Refresh Job ID

Developer identifier: jobs.extractRefreshJob_idExtract Refresh Job ID carries the source identifier named Extract Refresh Job ID for each job row. It is needed to resolve references that repeat the same provider identifier.

Enables: match job records to provider records that carry the same extract refresh job ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies extractRefreshJob_id as a record-level identifier on Jobs. It identifies Tableau catalog relationships and does not establish effective access. Tableau identifiers and view metadata do not prove effective access.

Developer identifier: jobs.idID is the declared record key for each job row. It supplies the declared record identity used when repeated ingestions represent the same source row.

Enables: recognize repeated ingestions of the same job source row before constructing its represented state.
Interpretation: The provider supplies id at one value per job record, and x-transformDedupKey explicitly marks it as the record key. Tableau identifiers and view metadata do not prove effective access.

Job Type

Developer identifier: jobs.jobTypeJob Type carries the source state or classification named Job Type for each job row. It preserves the provider’s current classification of this record.

Enables: separate job records by the exact provider-reported job type value when describing their recorded state.
Interpretation: The provider supplies jobType per job record using its own state vocabulary; unknown and missing values must remain distinct.

Priority

Developer identifier: jobs.priorityPriority carries the source state or classification named Priority for each job row. It preserves the provider’s current classification of this record.

Enables: separate job records by the exact provider-reported priority value when describing their recorded state.
Interpretation: The provider supplies priority per job record using its own state vocabulary; unknown and missing values must remain distinct.

Progress

Developer identifier: jobs.progressProgress records Tableau’s numeric progress value for the job. It preserves the execution-state value returned by the provider.

Enables: distinguish jobs at different stages of execution after applying the scale used by the source export.
Interpretation: The provider supplies progress as an integer but this schema does not declare its range or unit; zero and missing are not interchangeable.

Started At

Developer identifier: jobs.startedAtStarted At carries the source date or timestamp named Started At for each job row. It anchors the named event or boundary on the record’s timeline.

Enables: place job records on a timeline by started at and select the records within an explicit reporting window.
Interpretation: The provider supplies startedAt per job record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.

Status

Developer identifier: jobs.statusStatus carries the source state or classification named Status for each job row. It preserves the provider’s current classification of this record.

Enables: separate job records by the exact provider-reported status value when describing their recorded state.
Interpretation: The provider supplies status per job record using its own state vocabulary; unknown and missing values must remain distinct.

Status Notes

Developer identifier: jobs.statusNotesStatus Notes carries the source state or classification named Status Notes for each job row. It preserves the provider’s current classification of this record.

Enables: separate job records by the exact provider-reported status notes value when describing their recorded state.
Interpretation: The provider supplies statusNotes per job record using its own state vocabulary; unknown and missing values must remain distinct.

Type

Developer identifier: jobs.typeType carries the source state or classification named Type for each job row. It preserves the provider’s current classification of this record.

Enables: separate job records by the exact provider-reported type value when describing their recorded state.
Interpretation: The provider supplies type per job record using its own state vocabulary; unknown and missing values must remain distinct.

Workbook ID

Developer identifier: jobs.workbook_idWorkbook ID carries the source identifier named Workbook ID for each job row. It is needed to resolve references that repeat the same provider identifier.

Enables: match job records to provider records that carry the same workbook ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies workbook_id as a record-level identifier on Jobs. It identifies Tableau catalog relationships and does not establish effective access. Tableau identifiers and view metadata do not prove effective access.

Projects

Developer identifier: projectsProjects contain Tableau projects.

Enables: organize published Tableau content by project.
Scope: Reads provider changes through GET /api/{apiVersion}/sites/{siteId}/projects using the declared incremental request boundary. Results are limited to objects returned for the authenticated Tableau site; identifiers and view metadata do not establish effective access.

Content Permissions

Developer identifier: projects.contentPermissionsContent Permissions carries the source access or role value named Content Permissions for each project row. It documents the access-related value reported for this object or membership.

Enables: describe the provider-reported content permissions attached to each project record.
Interpretation: The provider supplies contentPermissions at project granularity. For Tableau, this metadata does not prove effective access.

Created At

Developer identifier: projects.createdAtCreated At carries the source date or timestamp named Created At for each project row. It anchors the named event or boundary on the record’s timeline.

Enables: place project records on a timeline by created at and select the records within an explicit reporting window.
Interpretation: The provider supplies createdAt per project record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.

Description

Developer identifier: projects.descriptionDescription carries the source-authored value named Description for each project row. It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact description value attached to each project record.
Interpretation: The provider supplies description at project granularity in the format stated by its description; omitted or redacted content remains unknown.

Developer identifier: projects.idID identifies Tableau LUID. It supplies the declared record identity used when repeated ingestions represent the same source row.

Enables: recognize repeated ingestions of the same project source row before constructing its represented state.
Interpretation: The provider supplies id at one value per project record, and x-transformDedupKey explicitly marks it as the record key. Tableau identifiers and view metadata do not prove effective access.

Name

Developer identifier: projects.nameName carries the source-authored value named Name for each project row. It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact name value attached to each project record.
Interpretation: The provider supplies name at project granularity in the format stated by its description; omitted or redacted content remains unknown.

Owner ID

Developer identifier: projects.owner_idOwner ID carries the source identifier named Owner ID for each project row. It is needed to resolve references that repeat the same provider identifier.

Enables: match project records to provider records that carry the same owner ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies owner_id as a record-level identifier on Projects. It identifies Tableau catalog relationships and does not establish effective access. Tableau identifiers and view metadata do not prove effective access.

Parent Project ID

Developer identifier: projects.parentProjectIdParent Project ID carries the source identifier named Parent Project ID for each project row. It is needed to resolve references that repeat the same provider identifier.

Enables: match project records to provider records that carry the same parent project ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies parentProjectId as a record-level identifier on Projects. It identifies Tableau catalog relationships and does not establish effective access. Tableau identifiers and view metadata do not prove effective access.

Top Level Project

Developer identifier: projects.topLevelProjectTop Level Project carries the source true-or-false flag named Top Level Project for each project row. It preserves the provider-reported yes-or-no condition for this record.

Enables: select project records for which the provider reports top level project as true or false.
Interpretation: The provider supplies topLevelProject as a boolean per project record; false and missing are distinct when the field is optional.

Updated At

Developer identifier: projects.updatedAtUpdated At carries the source date or timestamp named Updated At for each project row. It anchors the named event or boundary on the record’s timeline.

Enables: place project records on a timeline by updated at and select the records within an explicit reporting window.
Interpretation: The provider supplies updatedAt per project record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.

Writeable

Developer identifier: projects.writeableWriteable carries the source access or role value named Writeable for each project row. It documents the access-related value reported for this object or membership.

Enables: describe the provider-reported writeable attached to each project record.
Interpretation: The provider supplies writeable at project granularity. For Tableau, this metadata does not prove effective access.

Schedules

Developer identifier: schedulesSchedules contain server schedules (Tableau Server only; not available on Tableau Cloud).

Enables: review Tableau Server schedule cadence and next-run metadata.
Scope: Reads the declared collection through GET /api/{apiVersion}/schedules as a full snapshot. This endpoint is Tableau Server-only; Tableau Cloud schedules are outside its scope.

Created At

Developer identifier: schedules.createdAtCreated At carries the source date or timestamp named Created At for each schedule row. It anchors the named event or boundary on the record’s timeline.

Enables: place schedule records on a timeline by created at and select the records within an explicit reporting window.
Interpretation: The provider supplies createdAt per schedule record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.

Execution Order

Developer identifier: schedules.executionOrderExecution Order carries the source measure named Execution Order for each schedule row. It preserves the stated measure at this record’s granularity.

Enables: order or classify schedule records using the provider-defined execution order value.
Interpretation: The provider supplies executionOrder at schedule granularity as a provider-defined ordinal or planning value rather than elapsed time or money; zero and missing are not interchangeable.

Frequency

Developer identifier: schedules.frequencyFrequency carries the source period or schedule value named Frequency for each schedule row. It preserves the provider-defined period or schedule cadence for this record.

Enables: group schedule records by the provider-defined frequency period or schedule.
Interpretation: The provider supplies frequency per schedule record using its own period or schedule vocabulary; it is not an elapsed-duration measurement.

Developer identifier: schedules.idID identifies Tableau LUID. It supplies the declared record identity used when repeated ingestions represent the same source row.

Enables: recognize repeated ingestions of the same schedule source row before constructing its represented state.
Interpretation: The provider supplies id at one value per schedule record, and x-transformDedupKey explicitly marks it as the record key. Tableau identifiers and view metadata do not prove effective access.

Name

Developer identifier: schedules.nameName carries the source-authored value named Name for each schedule row. It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact name value attached to each schedule record.
Interpretation: The provider supplies name at schedule granularity in the format stated by its description; omitted or redacted content remains unknown.

Next Run At

Developer identifier: schedules.nextRunAtNext Run At carries the source date or timestamp named Next Run At for each schedule row. It anchors the named event or boundary on the record’s timeline.

Enables: place schedule records on a timeline by next run at and select the records within an explicit reporting window.
Interpretation: The provider supplies nextRunAt per schedule record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.

Priority

Developer identifier: schedules.priorityPriority carries the source state or classification named Priority for each schedule row. It preserves the provider’s current classification of this record.

Enables: separate schedule records by the exact provider-reported priority value when describing their recorded state.
Interpretation: The provider supplies priority per schedule record using its own state vocabulary; unknown and missing values must remain distinct.

State

Developer identifier: schedules.stateState carries the source state or classification named State for each schedule row. It preserves the provider’s current classification of this record.

Enables: separate schedule records by the exact provider-reported state value when describing their recorded state.
Interpretation: The provider supplies state per schedule record using its own state vocabulary; unknown and missing values must remain distinct.

Type

Developer identifier: schedules.typeType carries the source state or classification named Type for each schedule row. It preserves the provider’s current classification of this record.

Enables: separate schedule records by the exact provider-reported type value when describing their recorded state.
Interpretation: The provider supplies type per schedule record using its own state vocabulary; unknown and missing values must remain distinct.

Updated At

Developer identifier: schedules.updatedAtUpdated At carries the source date or timestamp named Updated At for each schedule row. It anchors the named event or boundary on the record’s timeline.

Enables: place schedule records on a timeline by updated at and select the records within an explicit reporting window.
Interpretation: The provider supplies updatedAt per schedule record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.

Subscriptions

Developer identifier: subscriptionsSubscriptions contain content subscriptions.

Enables: review content subscription recipients, schedules, and attachment options.
Scope: Reads the declared collection through GET /api/{apiVersion}/sites/{siteId}/subscriptions as a full snapshot. Results are limited to objects returned for the authenticated Tableau site; identifiers and view metadata do not establish effective access.

Attach Image

Developer identifier: subscriptions.attachImageAttach Image carries the provider-reported attach image for each subscription record. It retains the exact provider location for the referenced resource.

Enables: open or trace the exact provider resource referenced by attach image on a subscription record.
Interpretation: The provider supplies attachImage as a URL or resource locator on each subscription record. It identifies a Tableau catalog location but does not prove who can open it.

Attach PDF

Developer identifier: subscriptions.attachPdfAttach PDF carries the source true-or-false flag named Attach PDF for each subscription row. It preserves the provider-reported yes-or-no condition for this record.

Enables: select subscription records for which the provider reports attach PDF as true or false.
Interpretation: The provider supplies attachPdf as a boolean per subscription record; false and missing are distinct when the field is optional.

Content ID

Developer identifier: subscriptions.content_idContent ID carries the source identifier named Content ID for each subscription row. It is needed to resolve references that repeat the same provider identifier.

Enables: match subscription records to provider records that carry the same content ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies content_id as a record-level identifier on Subscriptions. It identifies Tableau catalog relationships and does not establish effective access. Tableau identifiers and view metadata do not prove effective access.

Content Type

Developer identifier: subscriptions.content_typeContent Type carries the source state or classification named Content Type for each subscription row. It preserves the provider’s current classification of this record.

Enables: separate subscription records by the exact provider-reported content type value when describing their recorded state.
Interpretation: The provider supplies content_type per subscription record using its own state vocabulary; unknown and missing values must remain distinct.

Developer identifier: subscriptions.idID is the declared record key for each subscription row. It supplies the declared record identity used when repeated ingestions represent the same source row.

Enables: recognize repeated ingestions of the same subscription source row before constructing its represented state.
Interpretation: The provider supplies id at one value per subscription record, and x-transformDedupKey explicitly marks it as the record key. Tableau identifiers and view metadata do not prove effective access.

Message

Developer identifier: subscriptions.messageMessage carries the source-authored value named Message for each subscription row. It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact message value attached to each subscription record.
Interpretation: The provider supplies message at subscription granularity in the format stated by its description; omitted or redacted content remains unknown.

Schedule Frequency

Developer identifier: subscriptions.schedule_frequencySchedule Frequency carries the source period or schedule value named Schedule Frequency for each subscription row. It preserves the provider-defined period or schedule cadence for this record.

Enables: group subscription records by the provider-defined schedule frequency period or schedule.
Interpretation: The provider supplies schedule_frequency per subscription record using its own period or schedule vocabulary; it is not an elapsed-duration measurement.

Schedule ID

Developer identifier: subscriptions.schedule_idSchedule ID carries the source identifier named Schedule ID for each subscription row. It is needed to resolve references that repeat the same provider identifier.

Enables: match subscription records to provider records that carry the same schedule ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies schedule_id as a record-level identifier on Subscriptions. It identifies Tableau catalog relationships and does not establish effective access. Tableau identifiers and view metadata do not prove effective access.

Schedule Name

Developer identifier: subscriptions.schedule_nameSchedule Name carries the source-authored value named Schedule Name for each subscription row. It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact schedule name value attached to each subscription record.
Interpretation: The provider supplies schedule_name at subscription granularity in the format stated by its description; omitted or redacted content remains unknown.

Subject

Developer identifier: subscriptions.subjectSubject carries the source-authored value named Subject for each subscription row. It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact subject value attached to each subscription record.
Interpretation: The provider supplies subject at subscription granularity in the format stated by its description; omitted or redacted content remains unknown.

Suspended

Developer identifier: subscriptions.suspendedSuspended carries the source true-or-false flag named Suspended for each subscription row. It preserves the provider-reported yes-or-no condition for this record.

Enables: select subscription records for which the provider reports suspended as true or false.
Interpretation: The provider supplies suspended as a boolean per subscription record; false and missing are distinct when the field is optional.

User ID

Developer identifier: subscriptions.user_idUser ID carries the source identifier named User ID for each subscription row. It is needed to resolve references that repeat the same provider identifier.

Enables: match subscription records to provider records that carry the same user ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies user_id as a record-level identifier on Subscriptions. It identifies Tableau catalog relationships and does not establish effective access. Tableau identifiers and view metadata do not prove effective access.

User Name

Developer identifier: subscriptions.user_nameUser Name carries the source person or account value named User Name for each subscription row. It keeps the provider-reported person or account context attached to the record.

Enables: attribute the subscription record to the provider-reported actor represented by user name.
Interpretation: The provider supplies user_name as identity or attribution context on each subscription record. Names and contact values can change and are not stable identifiers unless the provider documents them as such.

Users

Developer identifier: usersUsers contain Tableau site users.

Enables: inventory accounts returned for the configured Tableau site.
Scope: Reads the declared collection through GET /api/{apiVersion}/sites/{siteId}/users as a full snapshot. Results are limited to objects returned for the authenticated Tableau site; identifiers and view metadata do not establish effective access.

Auth Setting

Developer identifier: users.authSettingAuth Setting carries the source access or role value named Auth Setting for each user row. It documents the access-related value reported for this object or membership.

Enables: describe the provider-reported auth setting attached to each user record.
Interpretation: The provider supplies authSetting at user granularity. For Tableau, this metadata does not prove effective access.

External Auth User ID

Developer identifier: users.externalAuthUserIdExternal Auth User ID carries the source identifier named External Auth User ID for each user row. It is needed to resolve references that repeat the same provider identifier.

Enables: match user records to provider records that carry the same external auth user ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies externalAuthUserId as a record-level identifier on Users. It identifies Tableau catalog relationships and does not establish effective access. Tableau identifiers and view metadata do not prove effective access.

Developer identifier: users.idID identifies Tableau LUID. Kept as string (not Identity.UUID) so the Bronze II scalar hook does not base62-encode it; silver users.id must equal activity_events.actor_user_luid (PARABLE-3291). Same rationale as Microsoft GUIDs in microsoft.json. It supplies the declared record identity used when repeated ingestions represent the same source row.

Enables: recognize repeated ingestions of the same user source row before constructing its represented state.
Interpretation: The provider supplies id at one value per user record, and x-transformDedupKey explicitly marks it as the record key. Tableau identifiers and view metadata do not prove effective access.

Language

Developer identifier: users.languageLanguage carries the source location or localization value named Language for each user row. It preserves the geographic, locale, time-zone, or coordinate context represented by the field.

Enables: interpret dates, times, or localized text for users using the recorded language.
Interpretation: The provider supplies language as location or localization context per user record; it does not establish a person’s real-time physical location.

Last Login

Developer identifier: users.lastLoginLast Login carries the source date or timestamp named Last Login for each user row. It anchors the named event or boundary on the record’s timeline.

Enables: place user records on a timeline by last login and select the records within an explicit reporting window.
Interpretation: The provider supplies lastLogin per user record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.

Locale

Developer identifier: users.localeLocale carries the source location or localization value named Locale for each user row. It preserves the geographic, locale, time-zone, or coordinate context represented by the field.

Enables: interpret dates, times, or localized text for users using the recorded locale.
Interpretation: The provider supplies locale as location or localization context per user record; it does not establish a person’s real-time physical location.

Name

Developer identifier: users.nameName carries the source-authored value named Name for each user row. It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact name value attached to each user record.
Interpretation: The provider supplies name at user granularity in the format stated by its description; omitted or redacted content remains unknown.

Site Role

Developer identifier: users.siteRoleSite Role carries the source access or role value named Site Role for each user row. It documents the access-related value reported for this object or membership.

Enables: describe the provider-reported site role attached to each user record.
Interpretation: The provider supplies siteRole at user granularity. For Tableau, this metadata does not prove effective access.

Views

Developer identifier: viewsViews contain Tableau views/dashboards on a site.

Enables: catalog site views and dashboards with their workbook and usage metadata.
Scope: Reads provider changes through GET /api/{apiVersion}/sites/{siteId}/views using the declared incremental request boundary. Results are limited to objects returned for the authenticated Tableau site; identifiers and view metadata do not establish effective access.

Content URL

Developer identifier: views.contentUrlContent URL carries the provider-reported content url for each view record. It retains the exact provider location for the referenced resource.

Enables: open or trace the exact provider resource referenced by content URL on a view record.
Interpretation: The provider supplies contentUrl as a URL or resource locator on each view record. It identifies a Tableau catalog location but does not prove who can open it. Tableau identifiers and view metadata do not prove effective access.

Created At

Developer identifier: views.createdAtCreated At carries the source date or timestamp named Created At for each view row. It anchors the named event or boundary on the record’s timeline.

Enables: place view records on a timeline by created at and select the records within an explicit reporting window.
Interpretation: The provider supplies createdAt per view record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported. Tableau identifiers and view metadata do not prove effective access.

Developer identifier: views.idID identifies Tableau LUID. It supplies the declared record identity used when repeated ingestions represent the same source row.

Enables: recognize repeated ingestions of the same view source row before constructing its represented state.
Interpretation: The provider supplies id at one value per view record, and x-transformDedupKey explicitly marks it as the record key. Tableau identifiers and view metadata do not prove effective access.

Name

Developer identifier: views.nameName carries the source-authored value named Name for each view row. It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact name value attached to each view record.
Interpretation: The provider supplies name at view granularity in the format stated by its description; omitted or redacted content remains unknown. Tableau identifiers and view metadata do not prove effective access.

Owner ID

Developer identifier: views.owner_idOwner ID carries the source identifier named Owner ID for each view row. It is needed to resolve references that repeat the same provider identifier.

Enables: match view records to provider records that carry the same owner ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies owner_id as a record-level identifier on Views. It identifies Tableau catalog relationships and does not establish effective access. Tableau identifiers and view metadata do not prove effective access.

Project ID

Developer identifier: views.project_idProject ID carries the source identifier named Project ID for each view row. It is needed to resolve references that repeat the same provider identifier.

Enables: match view records to provider records that carry the same project ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies project_id as a record-level identifier on Views. It identifies Tableau catalog relationships and does not establish effective access. Tableau identifiers and view metadata do not prove effective access.

Updated At

Developer identifier: views.updatedAtUpdated At carries the source date or timestamp named Updated At for each view row. It anchors the named event or boundary on the record’s timeline.

Enables: place view records on a timeline by updated at and select the records within an explicit reporting window.
Interpretation: The provider supplies updatedAt per view record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported. Tableau identifiers and view metadata do not prove effective access.

Usage Total View Count

Developer identifier: views.usage_totalViewCountUsage Total View Count carries the source measure named Usage Total View Count for each view row. It preserves the stated measure at this record’s granularity.

Enables: measure the provider-reported usage total view count for each view record.
Interpretation: The provider supplies usage_totalViewCount at view granularity as a count at one value per record; zero and missing are not interchangeable. Tableau identifiers and view metadata do not prove effective access.

View URL Name

Developer identifier: views.viewUrlNameView URL Name carries the provider-reported view url name for each view record. It retains the exact provider location for the referenced resource.

Enables: open or trace the exact provider resource referenced by view URL name on a view record.
Interpretation: The provider supplies viewUrlName as a URL or resource locator on each view record. It identifies a Tableau catalog location but does not prove who can open it. Tableau identifiers and view metadata do not prove effective access.

Workbook ID

Developer identifier: views.workbook_idWorkbook ID carries the source identifier named Workbook ID for each view row. It is needed to resolve references that repeat the same provider identifier.

Enables: match view records to provider records that carry the same workbook ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies workbook_id as a record-level identifier on Views. It identifies Tableau catalog relationships and does not establish effective access. Tableau identifiers and view metadata do not prove effective access.

Workbook Views

Developer identifier: workbook_viewsWorkbook Views contain views nested under a workbook (opt-in; site views is default).

Enables: enumerate the views nested under an opted-in workbook.
Scope: Reads the declared collection through GET /api/{apiVersion}/sites/{siteId}/workbooks/{workbook_id}/views as a full snapshot. This child operation is opt-in and returns views for the selected parent workbook only.

Content URL

Developer identifier: workbook_views.contentUrlContent URL carries the provider-reported content url for each workbook view record. It retains the exact provider location for the referenced resource.

Enables: open or trace the exact provider resource referenced by content URL on a workbook view record.
Interpretation: The provider supplies contentUrl as a URL or resource locator on each workbook view record. It identifies a Tableau catalog location but does not prove who can open it. Tableau identifiers and view metadata do not prove effective access.

Created At

Developer identifier: workbook_views.createdAtCreated At carries the source date or timestamp named Created At for each workbook view row. It anchors the named event or boundary on the record’s timeline.

Enables: place workbook view records on a timeline by created at and select the records within an explicit reporting window.
Interpretation: The provider supplies createdAt per workbook view record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported. Tableau identifiers and view metadata do not prove effective access.

Developer identifier: workbook_views.idID identifies Tableau LUID. It supplies the declared record identity used when repeated ingestions represent the same source row.

Enables: recognize repeated ingestions of the same workbook view source row before constructing its represented state.
Interpretation: The provider supplies id at one value per workbook view record, and x-transformDedupKey explicitly marks it as the record key. Tableau identifiers and view metadata do not prove effective access.

Name

Developer identifier: workbook_views.nameName carries the source-authored value named Name for each workbook view row. It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact name value attached to each workbook view record.
Interpretation: The provider supplies name at workbook view granularity in the format stated by its description; omitted or redacted content remains unknown. Tableau identifiers and view metadata do not prove effective access.

Updated At

Developer identifier: workbook_views.updatedAtUpdated At carries the source date or timestamp named Updated At for each workbook view row. It anchors the named event or boundary on the record’s timeline.

Enables: place workbook view records on a timeline by updated at and select the records within an explicit reporting window.
Interpretation: The provider supplies updatedAt per workbook view record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported. Tableau identifiers and view metadata do not prove effective access.

Workbook ID

Developer identifier: workbook_views.workbook_idWorkbook ID carries the source identifier named Workbook ID for each workbook view row. It is needed to resolve references that repeat the same provider identifier.

Enables: match workbook view records to provider records that carry the same workbook ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies workbook_id as a record-level identifier on WorkbookViews. It identifies Tableau catalog relationships and does not establish effective access. Tableau identifiers and view metadata do not prove effective access.

Workbooks

Developer identifier: workbooksWorkbooks contain published Tableau workbooks.

Enables: catalog published workbooks with their project, owner, size, and modification metadata.
Scope: Reads provider changes through GET /api/{apiVersion}/sites/{siteId}/workbooks using the declared incremental request boundary. Results are limited to objects returned for the authenticated Tableau site; identifiers and view metadata do not establish effective access.

Content URL

Developer identifier: workbooks.contentUrlContent URL carries the provider-reported content url for each workbook record. It retains the exact provider location for the referenced resource.

Enables: open or trace the exact provider resource referenced by content URL on a workbook record.
Interpretation: The provider supplies contentUrl as a URL or resource locator on each workbook record. It identifies a Tableau catalog location but does not prove who can open it.

Created At

Developer identifier: workbooks.createdAtCreated At carries the source date or timestamp named Created At for each workbook row. It anchors the named event or boundary on the record’s timeline.

Enables: place workbook records on a timeline by created at and select the records within an explicit reporting window.
Interpretation: The provider supplies createdAt per workbook record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.

Default View ID

Developer identifier: workbooks.defaultViewIdDefault View ID carries the source identifier named Default View ID for each workbook row. It is needed to resolve references that repeat the same provider identifier.

Enables: match workbook records to provider records that carry the same default view ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies defaultViewId as a record-level identifier on Workbooks. It identifies Tableau catalog relationships and does not establish effective access. Tableau identifiers and view metadata do not prove effective access.

Description

Developer identifier: workbooks.descriptionDescription carries the source-authored value named Description for each workbook row. It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact description value attached to each workbook record.
Interpretation: The provider supplies description at workbook granularity in the format stated by its description; omitted or redacted content remains unknown.

Encrypt Extracts

Developer identifier: workbooks.encryptExtractsEncrypt Extracts carries the source true-or-false flag named Encrypt Extracts for each workbook row. It preserves the provider-reported yes-or-no condition for this record.

Enables: select workbook records for which the provider reports encrypt extracts as true or false.
Interpretation: The provider supplies encryptExtracts as a boolean per workbook record; false and missing are distinct when the field is optional.

Developer identifier: workbooks.idID identifies Tableau LUID. It supplies the declared record identity used when repeated ingestions represent the same source row.

Enables: recognize repeated ingestions of the same workbook source row before constructing its represented state.
Interpretation: The provider supplies id at one value per workbook record, and x-transformDedupKey explicitly marks it as the record key. Tableau identifiers and view metadata do not prove effective access.

Name

Developer identifier: workbooks.nameName carries the source-authored value named Name for each workbook row. It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact name value attached to each workbook record.
Interpretation: The provider supplies name at workbook granularity in the format stated by its description; omitted or redacted content remains unknown.

Owner ID

Developer identifier: workbooks.owner_idOwner ID carries the source identifier named Owner ID for each workbook row. It is needed to resolve references that repeat the same provider identifier.

Enables: match workbook records to provider records that carry the same owner ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies owner_id as a record-level identifier on Workbooks. It identifies Tableau catalog relationships and does not establish effective access. Tableau identifiers and view metadata do not prove effective access.

Owner Name

Developer identifier: workbooks.owner_nameOwner Name carries the source person or account value named Owner Name for each workbook row. It keeps the provider-reported person or account context attached to the record.

Enables: attribute the workbook record to the provider-reported actor represented by owner name.
Interpretation: The provider supplies owner_name as identity or attribution context on each workbook record. Names and contact values can change and are not stable identifiers unless the provider documents them as such.

Project ID

Developer identifier: workbooks.project_idProject ID carries the source identifier named Project ID for each workbook row. It is needed to resolve references that repeat the same provider identifier.

Enables: match workbook records to provider records that carry the same project ID, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies project_id as a record-level identifier on Workbooks. It identifies Tableau catalog relationships and does not establish effective access. Tableau identifiers and view metadata do not prove effective access.

Project Name

Developer identifier: workbooks.project_nameProject Name carries the source-authored value named Project Name for each workbook row. It keeps the exact text, label, or authored value needed to interpret the record.

Enables: inspect the exact project name value attached to each workbook record.
Interpretation: The provider supplies project_name at workbook granularity in the format stated by its description; omitted or redacted content remains unknown.

Show Tabs

Developer identifier: workbooks.showTabsShow Tabs carries the source true-or-false flag named Show Tabs for each workbook row. It preserves the provider-reported yes-or-no condition for this record.

Enables: select workbook records for which the provider reports show tabs as true or false.
Interpretation: The provider supplies showTabs as a boolean per workbook record; false and missing are distinct when the field is optional.

Size

Developer identifier: workbooks.sizeSize records Tableau’s numeric size attribute for the workbook. It preserves the source value even though this schema does not declare its unit.

Enables: compare workbook size values within exports that use the same Tableau definition and source configuration.
Interpretation: The provider supplies size as an integer with no unit documented here; do not assume bytes, row count, or another scale without provider context.

Updated At

Developer identifier: workbooks.updatedAtUpdated At carries the source date or timestamp named Updated At for each workbook row. It anchors the named event or boundary on the record’s timeline.

Enables: place workbook records on a timeline by updated at and select the records within an explicit reporting window.
Interpretation: The provider supplies updatedAt per workbook record as a timestamp at the precision returned by the provider; missing values mean the event or boundary was not reported.

Personal Access Token (recommended)

Error	Meaning	Solution
`401 Unauthorized`	Invalid PAT or expired session	Recreate PAT; confirm tokens are enabled
`403 Forbidden`	Insufficient permissions	Use a Site Administrator PAT
`404 Site not found`	Wrong site content URL	Fix Site Name (content URL slug, not display name)

PATs disabled

Personal Access Tokens must be enabled by a server/site admin.Signing in again with the same PAT can invalidate the previous session. A Tableau sync reuses one signed-in session across its concurrent data streams; if multiple Parable connections use the same PAT, keep them on separate schedules or use a distinct PAT for each connection.Tableau REST API — Official API documentation

Connected Apps (Direct Trust JWT)

Error	Meaning	Solution
`401 Unauthorized` on sign-in	Bad JWT claims/secret or disabled app	Regenerate secret; confirm `sub` email exists; confirm app is enabled
`403 Forbidden`	Missing JWT scope or site role	Add required `scp` values; use a user with sufficient site role
Wrong site	contentUrl mismatch	Fix Site Name (content URL slug)

Configure Connected Apps with Direct Trust — Official Tableau docs

Username and password (Tableau Server)

Error	Meaning	Solution
`401 Unauthorized`	Bad username/password or MFA challenge	Use PAT instead; confirm account is not MFA-gated
`403 Forbidden`	Insufficient site role	Use a higher-privileged Server user

Tableau REST API authentication — Official docs

​Personal Access Token (recommended)

​Content

​Usage and users

​Connected Apps (Direct Trust JWT)

​Username and password (Tableau Server)

​Data streams

​Personal Access Token (recommended)

​What You’ll Need

​Step 1: Access Account Settings

​Step 2: Create Personal Access Token

​Step 3: Note your server details

​Step 4: Enter values in Parable

​Connected Apps (Direct Trust JWT)

​What You’ll Need

​Step 1: Create a Connected App (Direct Trust)

​Step 2: Note site and server details

​Step 3: Enter values in Parable

​Username and password (Tableau Server)

​What You’ll Need

​Step 1: Confirm password sign-in works on your server

​Step 2: Note server details

​Step 3: Enter values in Parable

​Personal Access Token (recommended)

​PATs disabled

​Concurrent sign-in

​Connected Apps (Direct Trust JWT)

​Username and password (Tableau Server)

Personal Access Token (recommended)

Content

Usage and users

Connected Apps (Direct Trust JWT)

Username and password (Tableau Server)

Data streams

Personal Access Token (recommended)

What You’ll Need

Step 1: Access Account Settings

Step 2: Create Personal Access Token

Step 3: Note your server details

Step 4: Enter values in Parable

Connected Apps (Direct Trust JWT)

What You’ll Need

Step 1: Create a Connected App (Direct Trust)

Step 2: Note site and server details

Step 3: Enter values in Parable

Username and password (Tableau Server)

What You’ll Need

Step 1: Confirm password sign-in works on your server

Step 2: Note server details

Step 3: Enter values in Parable

Personal Access Token (recommended)

PATs disabled

Concurrent sign-in

Connected Apps (Direct Trust JWT)

Username and password (Tableau Server)