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 signs in with the token and finds your site 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 signs a short-lived token with the Connected App secret and uses it to sign in. This is not browser OAuth (no authorize redirect).

Username and password (Tableau Server)

Connect Parable to Tableau Server with username and password.

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

Data streams

This Provider Plugin defines 19 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
`user_workbooks`	The workbooks each licensed Tableau user can open	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

Source permissions

When your Workspace enforces source permissions, each member reads only the Tableau rows that their Tableau user can open. Parable matches a member to a Tableau user by email. Only a user with a licensed site role (Creator, Explorer, Explorer (can publish), Viewer, a site administrator role, or a server administrator) gives access. An Unlicensed user, a guest, or a user whose site role Tableau leaves out gives no access.

Data	Who reads it
`workbooks`, `views`, `workbook_views`	The users that Tableau lists as able to open the workbook (`user_workbooks`). A view follows its workbook.
`custom_views`	The owner. A shared custom view also opens to the readers of its view.
`projects`, `datasources`, `datasource_connections`, `flows`	The owner of the project, data source or flow.
`subscriptions`, `activity_events`	The user the subscription is for, and the user who performed the event.
`users`, `groups`, `group_users`, `user_workbooks`, `jobs`, `extract_refresh_tasks`, `schedules`, `flow_tasks`, `flow_runs`	Only people with All data access.

Parable does not read Tableau’s permission rules for projects, data sources and flows yet. Until it does, a user who can open one of them in Tableau through a rule, and does not own it, does not read it in Parable. A view of a workbook with hidden tabs follows its workbook, even when Tableau gives the view its own rules.user_workbooks sends at least one request for each licensed user on each sync. Use a site administrator credential, so that Tableau returns the list for every user.

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 (to sync every data stream)

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

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, including tableau:users:read, which Save & test needs

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.

Note: Save & test asks Tableau only for tableau:users:read, the scope its users listing needs, whatever scopes you set in step 3. If your scopes leave out a scope a table needs, Save & test can pass while that table cannot sync.

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 a role that can read the data streams 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 the records that changed since the previous sync from GET /api/3.29/activity/events. 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 Tableau LUID of the user who performed the event. It is needed to resolve references that repeat the same provider identifier.

Enables: match activity event records to the actor’s row in users (users.id).
Interpretation: The provider supplies actorUserId as a site user LUID. For source permissions, each event opens to the user who performed it. An event with no actor opens only to readers with All data 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 record key for each activity event row. Rows with the same value describe the same record.

Enables: identify each activity event record across syncs.
Interpretation: The provider supplies id at one value per activity event record, and it is 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. 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 the records that changed since the previous sync from GET /api/3.29/sites/{siteId}/customviews. 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 is the record key, so rows with the same value describe the same record.

Enables: identify each custom view record across syncs.
Interpretation: The provider supplies id at one value per custom view record, and it is 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

Developer identifier: custom_views.ownerOwner. The user who saved the custom view, as Tableau’s nested owner element.

Enables: Attribute each custom view to its owner (owner.id to users.id).
Interpretation: For source permissions, the owner always reads their own custom view.

Developer identifier: custom_views.owner.idID. Tableau’s LUID of the user who owns the custom view.

Enables: Connect each custom view to its owner’s row in users (users.id).
Interpretation: Tableau returns the owner as a nested owner element with an id. The value is in the same namespace as users.id.

Name

Developer identifier: custom_views.owner.nameName. The Tableau user name of the custom view’s owner, when Tableau returns it.

Enables: Show who owns each custom view without a join to users.
Interpretation: A user name can change. Use owner.id to identify the owner.

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. For source permissions, a custom view inherits the access of its view only when shared is true. When it is false or missing, only the owner reads the custom view.

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

Developer identifier: custom_views.viewView. The view that the custom view is based on, as Tableau’s nested view element.

Enables: Associate each custom view with its view (view.id to views.id).
Interpretation: For source permissions, a shared custom view (shared true) also opens to each member who can open its view. A custom view that is not shared opens to its owner only.

Developer identifier: custom_views.view.idID. Tableau’s LUID of the view that the custom view is based on.

Enables: Connect each custom view to its view in views (views.id).
Interpretation: Every custom view is based on one view.

Name

Developer identifier: custom_views.view.nameName. The name of the view that the custom view is based on.

Enables: Show the source view without a join to views.
Interpretation: A view name can change. Use view.id to identify the view.

Workbook

Developer identifier: custom_views.workbookWorkbook. The workbook that holds the view, as Tableau’s nested workbook element.

Enables: Associate each custom view with its workbook (workbook.id to workbooks.id).
Interpretation: Source permissions read view, not this field.

Developer identifier: custom_views.workbook.idID. Tableau’s LUID of the workbook that holds the view.

Enables: Connect each custom view to its workbook in workbooks.
Interpretation: Source permissions read the view, not this field.

Name

Developer identifier: custom_views.workbook.nameName. The name of the workbook that holds the view.

Enables: Show the workbook without a join to workbooks.
Interpretation: A workbook name can change. Use workbook.id to identify it.

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 every record from GET /api/3.29/sites/{siteId}/datasources/{datasource_id}/connections on each sync. 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 the LUID of the parent datasource, which Parable copies from that record. 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. It identifies Tableau catalog relationships and does not establish effective access. Tableau identifiers and view metadata do not prove effective access. For source permissions, the connection inherits the access of this data source.

Developer identifier: datasource_connections.idID is the record key for each datasource connection row. Rows with the same value describe the same record.

Enables: identify each datasource connection record across syncs.
Interpretation: The provider supplies id at one value per datasource connection record, and it is 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; 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; 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 the records that changed since the previous sync from GET /api/3.29/sites/{siteId}/datasources. 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 is the record key, so rows with the same value describe the same record.

Enables: identify each datasource record across syncs.
Interpretation: The provider supplies id at one value per datasource record, and it is 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

Developer identifier: datasources.ownerOwner. The user who owns the data source, as Tableau’s nested owner element.

Enables: Attribute each data source to its owner (owner.id to users.id).
Interpretation: For source permissions, the owner reads the data source. Parable does not read Tableau’s permission rules for a data source yet, so no other member reads it, except readers with All data access.

Developer identifier: datasources.owner.idID. Tableau’s LUID of the user who owns the data source.

Enables: Connect each data source to its owner’s row in users (users.id).
Interpretation: Tableau returns the owner as a nested owner element with an id. The value is in the same namespace as users.id.

Name

Developer identifier: datasources.owner.nameName. The Tableau user name of the data source’s owner, when Tableau returns it.

Enables: Show who owns each data source without a join to users.
Interpretation: A user name can change. Use owner.id to identify the owner.

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. 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 every record from GET /api/3.29/sites/{siteId}/tasks/extractRefreshes on each sync. Results are limited to objects returned for the authenticated Tableau site; identifiers and view metadata do not establish effective access.

Extract Refresh

Developer identifier: extract_refresh_tasks.extractRefreshExtract Refresh records the extractRefresh task Tableau wraps each tasks.task element in. It carries the whole extract refresh task, whose record identity is extractRefresh.id.

Enables: read each extract refresh task record from the one object Tableau returns per tasks.task element.
Interpretation: The provider supplies extractRefresh at one value per extract refresh task record and puts no fields beside it; the task’s own fields are declared.

Consecutive Failed Count

Developer identifier: extract_refresh_tasks.extractRefresh.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

Developer identifier: extract_refresh_tasks.extractRefresh.datasourceDatasource carries the data source the task refreshes, when it targets a data source, as Tableau returns it for each extract refresh task row. It holds a nested object whose keys can vary.

Enables: match extract refresh task records to the data source they refresh by the identifier and name inside datasource, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies datasource at extract refresh task granularity only when the task targets a data source; keys and value shapes within it can vary with provider configuration. Tableau identifiers and view metadata do not prove effective access.

Developer identifier: extract_refresh_tasks.extractRefresh.idID is the task LUID Tableau returns for each extract refresh task row. It is the key of this nested record.

Enables: identify each extract refresh task record.
Interpretation: The provider supplies id at one value per extract refresh task record inside the extractRefresh object, and extractRefresh.id is the record key. Tableau identifiers and view metadata do not prove effective access.

Priority

Developer identifier: extract_refresh_tasks.extractRefresh.priorityPriority carries the source state or classification named Priority for each extract refresh task row.

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 as a number; unknown and missing values must remain distinct.

Schedule

Developer identifier: extract_refresh_tasks.extractRefresh.scheduleSchedule carries the schedule the task runs on (id, name, state, frequency, nextRunAt, frequencyDetails) as Tableau returns it for each extract refresh task row. It preserves the provider-defined cadence for this record.

Enables: group extract refresh task records by the provider-defined schedule and place their next run on a timeline from the values inside schedule.
Interpretation: The provider supplies schedule per extract refresh task record using its own period and state vocabulary; keys and value shapes within it can vary with provider configuration, and it is not an elapsed-duration measurement.

Type

Developer identifier: extract_refresh_tasks.extractRefresh.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

Developer identifier: extract_refresh_tasks.extractRefresh.workbookWorkbook carries the workbook the task refreshes, when it targets a workbook, as Tableau returns it for each extract refresh task row. It holds a nested object whose keys can vary.

Enables: match extract refresh task records to the workbook they refresh by the identifier and name inside workbook, without assuming that this field alone makes every row unique.
Interpretation: The provider supplies workbook at extract refresh task granularity only when the task targets a workbook; keys and value shapes within it can vary with provider configuration. Tableau identifiers and view metadata do not prove effective access.

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 the records that changed since the previous sync from GET /api/3.29/sites/{siteId}/flows/runs. 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. 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.

Enables: place flow run records on a timeline by completed at.
Interpretation: The provider supplies completedAt per flow run record as a timestamp; a missing value means the time was not reported.

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. 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 record key for each flow run row. Rows with the same value describe the same record.

Enables: identify each flow run record across syncs.
Interpretation: The provider supplies id at one value per flow run record, and it is 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 every record from GET /api/3.29/sites/{siteId}/tasks/flows on each sync. 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. 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 holds configured attributes whose keys and shapes can vary.

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. Check the keys in your Workspace’s data rather than assume a fixed set.

Developer identifier: flow_tasks.idID is the record key for each flow task row. Rows with the same value describe the same record.

Enables: identify each flow task record across syncs.
Interpretation: The provider supplies id at one value per flow task record, and it is 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.

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 as a number; 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. 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 the records that changed since the previous sync from GET /api/3.29/sites/{siteId}/flows. 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 is the record key, so rows with the same value describe the same record.

Enables: identify each flow record across syncs.
Interpretation: The provider supplies id at one value per flow record, and it is 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

Developer identifier: flows.ownerOwner. The user who owns the flow, as Tableau’s nested owner element.

Enables: Attribute each flow to its owner (owner.id to users.id).
Interpretation: For source permissions, the owner reads the flow. Parable does not read Tableau’s permission rules for a flow yet, so no other member reads it, except readers with All data access.

Developer identifier: flows.owner.idID. Tableau’s LUID of the user who owns the flow.

Enables: Connect each flow to its owner’s row in users (users.id).
Interpretation: Tableau returns the owner as a nested owner element with an id. The value is in the same namespace as users.id.

Name

Developer identifier: flows.owner.nameName. The Tableau user name of the flow’s owner, when Tableau returns it.

Enables: Show who owns each flow without a join to users.
Interpretation: A user name can change. Use owner.id to identify the owner.

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. 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 every record from GET /api/3.29/sites/{siteId}/groups/{group_id}/users on each sync. Results are limited to objects returned for the authenticated Tableau site; identifiers and view metadata do not establish effective access. With source permissions on, each row makes the user a member of the group, and only readers with All data access read this stream.

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 the LUID of the parent group, which Parable copies from that record. 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. 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. Tableau’s LUID for the user who belongs to the group.

Enables: Connect each group membership to the member’s Tableau account through group_users.id.
Interpretation: Tableau reports this value in its user namespace. The same value repeats once for every group the member belongs to, so it does not identify a row on its own.

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.

Membership Key

Developer identifier: group_users.membership_keyMembership Key. A key Parable builds from group_id and id, so each combination of those values has one key.

Enables: Identify each group membership on its own, so a member who belongs to several Tableau groups has one row per group.
Interpretation: Parable calculates membership_key when it reads the record. It identifies one group-to-member relationship, not the member or the group by itself, and is not a Tableau identifier. It is the record key.

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 every record from GET /api/3.29/sites/{siteId}/groups on each sync. Results are limited to objects returned for the authenticated Tableau site; identifiers and view metadata do not establish effective access. With source permissions on, each group is a principal, and only readers with All data access read this stream.

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 is the record key, so rows with the same value describe the same record.

Enables: identify each group record across syncs.
Interpretation: The provider supplies id at one value per group record, and it is 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 job type, status, priority, and created, started and ended times.
Scope: Reads the records that changed since the previous sync from GET /api/3.29/sites/{siteId}/jobs. Results are limited to objects returned for the authenticated Tableau site; identifiers and view metadata do not establish effective access.

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.

Ended At

Developer identifier: jobs.endedAtEnded At carries the time that Tableau reports for the end of each background job.

Enables: place job records on a timeline by ended at, and compare it with Started At to see how long a job ran.
Interpretation: The provider supplies endedAt per job record as a timestamp at the precision that the provider returns. A missing value means that the time was not reported.

Developer identifier: jobs.idID is the record key for each job row. Rows with the same value describe the same record.

Enables: identify each job record across syncs.
Interpretation: The provider supplies id at one value per job record, and it is 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.

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

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.

Projects

Developer identifier: projectsProjects contain Tableau projects.

Enables: organize published Tableau content by project.
Scope: Reads the records that changed since the previous sync from GET /api/3.29/sites/{siteId}/projects. 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 is the record key, so rows with the same value describe the same record.

Enables: identify each project record across syncs.
Interpretation: The provider supplies id at one value per project record, and it is 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

Developer identifier: projects.ownerOwner. The user who owns the project, as Tableau’s nested owner element.

Enables: Attribute each project to its owner (owner.id to users.id).
Interpretation: For source permissions, the owner reads the project. Parable does not read Tableau’s permission rules for a project yet, so no other member reads it, except readers with All data access.

Developer identifier: projects.owner.idID. Tableau’s LUID of the user who owns the project.

Enables: Connect each project to its owner’s row in users (users.id).
Interpretation: Tableau returns the owner as a nested owner element with an id. The value is in the same namespace as users.id.

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. 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 every record from GET /api/3.29/schedules on each sync. 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 is the record key, so rows with the same value describe the same record.

Enables: identify each schedule record across syncs.
Interpretation: The provider supplies id at one value per schedule record, and it is 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.

Enables: separate schedule records by the exact provider-reported priority value when describing their recorded state.
Interpretation: The provider supplies priority per schedule record as a number; 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 every record from GET /api/3.29/sites/{siteId}/subscriptions on each sync. 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. 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 record key for each subscription row. Rows with the same value describe the same record.

Enables: identify each subscription record across syncs.
Interpretation: The provider supplies id at one value per subscription record, and it is 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. 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

Developer identifier: subscriptions.userUser. The user who receives the subscription, as Tableau’s nested user element.

Enables: Attribute each subscription to its recipient (user.id to users.id).
Interpretation: Tableau shows a user who is not an administrator only their own subscriptions. For source permissions, each subscription opens to its user only.

Developer identifier: subscriptions.user.idID. Tableau’s LUID of the user who receives the subscription.

Enables: Connect each subscription to its user in users (users.id).
Interpretation: The value is in the same namespace as users.id.

Name

Developer identifier: subscriptions.user.nameName. The Tableau user name of the user who receives the subscription.

Enables: Show the recipient without a join to users.
Interpretation: A user name can change. Use user.id to identify the user.

User Workbooks

Developer identifier: user_workbooksUser Workbooks. One record for each licensed Tableau user and each workbook that the user owns or can view, as Tableau itself decides it.

Enables: With source permissions on, a Parable member reads each workbook, and its views, that Tableau lets their Tableau user open. Tableau’s answer already applies Deny rules, locked projects, owners, project leaders and site administrators. Only readers with All data access read this stream.
Scope: Reads every record from GET /api/3.29/sites/{siteId}/users/{user_id}/workbooks?ownedBy=false once for each user in users whose site role is not Unlicensed, on each sync. A site administrator credential reads the list of any user. A workbook absent from a later full read is no longer open to the user, and Parable marks the record deleted. Each sync sends at least one request for each licensed user.

Grant Key

Developer identifier: user_workbooks.grant_keyGrant Key. A key Parable builds from user_id and id, so each user and workbook pair has one key.

Enables: Identify each user’s access to one workbook on its own, so a workbook that several users can open has one row for each user.
Interpretation: Parable calculates grant_key when it reads the record. It is not a Tableau identifier. It is the record key.

Workbook ID

Developer identifier: user_workbooks.idWorkbook ID. Tableau’s LUID of a workbook that the user owns or can view.

Enables: Connect each grant to its workbook in workbooks (workbooks.id).
Interpretation: Tableau lists the workbook because the user has Read (view) access to it, or owns it. For source permissions, the workbook opens to the user, and so do its views.

Workbook Name

Developer identifier: user_workbooks.nameWorkbook Name. The name of the workbook that the user can open.

Enables: Read which workbooks each user can open without a join to workbooks.
Interpretation: A workbook name can change. Use id to identify the workbook.

User ID

Developer identifier: user_workbooks.user_idUser ID. Tableau’s LUID of the user whose workbooks Parable read, which Parable copies from the parent users record.

Enables: Connect each grant to the user in users (users.id).
Interpretation: The same user repeats once for each workbook that the user can open, so the value does not identify a row on its own. For source permissions, the row gives this user’s token to the workbook.

Users

Developer identifier: usersUsers contain Tableau site users.

Enables: inventory accounts returned for the configured Tableau site, and match each account to a Parable member by email for identity and source permissions.
Scope: Reads every record from GET /api/3.29/sites/{siteId}/users?fields=_default_,email on each sync, inactive (Unlicensed) users included. Tableau lets only server and site administrators list users. With source permissions on, only readers with All data access read this stream.

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.

Developer identifier: users.emailEmail. The email address of the Tableau user. Parable asks for it with fields=_default_,email, because Tableau does not return it by default.

Enables: Match each Tableau user to a Parable member by email, so source permissions know which Tableau rows the member can open.
Interpretation: Tableau can return no email for a user that has none, such as a local Tableau Server user. Such a user matches no member by email, so the member reads no Tableau row through that account.

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. 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. Parable keeps it as text in Tableau’s form, so it equals activity_events.actorUserId, user_workbooks.user_id and the owner IDs of other streams. It is the record key, so rows with the same value describe the same record.

Enables: identify each user record across syncs, and match the account to a Parable member through identity.
Interpretation: The provider supplies id at one value per user record, and it is the record key. For source permissions, each user is a principal: the token user:<id> opens the workbooks that user_workbooks lists for the user, and the rows that the user owns.

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. An Unlicensed user cannot sign in to Tableau. For source permissions, a user is active only with a licensed role: Creator, Explorer, ExplorerCanPublish, SiteAdministratorCreator, SiteAdministratorExplorer, Viewer or ServerAdministrator. Unlicensed, any other value, or a missing value makes the user inactive, and an inactive user gives no token.

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 the records that changed since the previous sync from GET /api/3.29/sites/{siteId}/views. 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 is the record key, so rows with the same value describe the same record.

Enables: identify each view record across syncs.
Interpretation: The provider supplies id at one value per view record, and it is 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

Developer identifier: views.ownerOwner. The user who owns the view, as Tableau’s nested owner element.

Enables: Attribute each view to its owner (owner.id to users.id).
Interpretation: The owner of a view is the owner of its workbook. Source permissions read the workbook, not this field.

Developer identifier: views.owner.idID. Tableau’s LUID of the user who owns the view.

Enables: Connect each view to its owner’s row in users (users.id).
Interpretation: Tableau returns the owner as a nested owner element with an id. The value is in the same namespace as users.id.

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. 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

Developer identifier: views.workbookWorkbook. The workbook that holds the view, as Tableau’s nested workbook element.

Enables: Associate each view with its workbook (workbook.id to workbooks.id).
Interpretation: For source permissions, a view inherits its workbook’s access: a member who can open the workbook reads its views. A view of a workbook with hidden tabs can have its own rules in Tableau. Parable does not read them, so the view follows its workbook.

Developer identifier: views.workbook.idID. Tableau’s LUID of the workbook that holds the view.

Enables: Connect each view to its workbook in workbooks (workbooks.id).
Interpretation: Every view belongs to one workbook.

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 every record from GET /api/3.29/sites/{siteId}/workbooks/{workbook_id}/views on each sync. 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 is the record key, so rows with the same value describe the same record.

Enables: identify each workbook view record across syncs.
Interpretation: The provider supplies id at one value per workbook view record, and it is 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. It identifies Tableau catalog relationships and does not establish effective access. Tableau identifiers and view metadata do not prove effective access. For source permissions, the view inherits the access of this workbook.

Workbooks

Developer identifier: workbooksWorkbooks contain published Tableau workbooks.

Enables: catalog published workbooks with their project, owner, size, and modification metadata.
Scope: Reads the records that changed since the previous sync from GET /api/3.29/sites/{siteId}/workbooks. With source permissions on, a member reads a workbook when user_workbooks lists it for their Tableau user. A workbook that no user can open, or that Tableau deleted, opens only to readers with All data 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. 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 is the record key, so rows with the same value describe the same record.

Enables: identify each workbook record across syncs.
Interpretation: The provider supplies id at one value per workbook record, and it is 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

Developer identifier: workbooks.ownerOwner. The user who owns the workbook, as Tableau’s nested owner element.

Enables: Attribute each workbook to its owner (owner.id to users.id).
Interpretation: Source permissions do not read this field: Tableau’s own list in user_workbooks already gives the owner the workbook.

Developer identifier: workbooks.owner.idID. Tableau’s LUID of the user who owns the workbook.

Enables: Connect each workbook to its owner’s row in users (users.id).
Interpretation: Tableau returns the owner as a nested owner element with an id. The value is in the same namespace as users.id.

Name

Developer identifier: workbooks.owner.nameName. The Tableau user name of the workbook’s owner, when Tableau returns it.

Enables: Show who owns each workbook without a join to users.
Interpretation: A user name can change. Use owner.id to identify the owner.

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. 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

​Source permissions

​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

Source permissions

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)