Glean requires authentication to the customer’s Tableau instance in order to fetch relevant Tableau permissions and content.
Glean uses Tableau’s Personal Access Token (PAT) flow for authentication. The user that goes through the initial authentication flow should be a Tableau admin. Thereafter, each user who wants to be able to search for Tableau content in Glean needs to authenticate individually via their Glean-connected app settings (see the Setup section below for more detail).
Glean understands all user access permissions and strictly enforces permissions for users at the time of the query. This ensures that users cannot see results they do not have access to.
Note that all data is stored in a GCP project inside the customer’s cloud account, and no data leaves the customer’s environment.
Glean crawlers default to the 3.16 version of Tableau’s API. Although this can be configured to a different version, please consult with Glean to determine if your version is compatible with our crawlers.
For Tableau, Glean indexes the following content and associated permissioning:
Note: Glean only crawls the metadata of these documents (id, name, owner, description for workspaces, createdAt/updatedAt). We don’t crawl the actual content of workbooks/data sources.
Tableau is both an online and on-prem version and the Glean-Tableau integration has been engineered to work with both right out of the box.
Glean uses the Tableau Server REST API to ingest all data:
Glean begins by understanding the users who are a part of the Tableau instance and their associated roles and permissions in the system.
Glean crawls all workbooks and data sources in the customer’s Tableau instance using the admin credentials granted in the initial authentication flow.
For each individually authenticated user, Glean performs additional processing to understand which users should be allowed to see each workbook and data source.
Those access policies are then enforced so there is parity between permissions for Tableau content in Glean and the original permissions in Tableau.
Glean performs a full crawl of the content monthly and makes use of incremental crawls to update existing content and permissions several times every hour.
A Tableau admin is required to go through the initial authentication flow to connect Glean with Tableau. The initial authentication flow provides Glean credentials with which to access the Tableau Server REST API on behalf of the customer.
Instructions are provided onscreen in the deployment console, but a summary is also provided here:
Determine the domain and site content URL of your Tableau instance:
Generate a Personal Access Token (PAT):
Users who want to start accessing Tableau search results in Glean need to authenticate individually by following these steps:
Glean allows configuring for only a certain user set to have access to Tableau search results.
For any questions or issues with this setup, please reach out to support@glean.com.
Glean requires authentication to the customer’s Tableau instance in order to fetch relevant Tableau permissions and content.
Glean uses Tableau’s Personal Access Token (PAT) flow for authentication. The user that goes through the initial authentication flow should be a Tableau admin. Thereafter, each user who wants to be able to search for Tableau content in Glean needs to authenticate individually via their Glean-connected app settings (see the Setup section below for more detail).
Glean understands all user access permissions and strictly enforces permissions for users at the time of the query. This ensures that users cannot see results they do not have access to.
Note that all data is stored in a GCP project inside the customer’s cloud account, and no data leaves the customer’s environment.
Glean crawlers default to the 3.16 version of Tableau’s API. Although this can be configured to a different version, please consult with Glean to determine if your version is compatible with our crawlers.
For Tableau, Glean indexes the following content and associated permissioning:
Note: Glean only crawls the metadata of these documents (id, name, owner, description for workspaces, createdAt/updatedAt). We don’t crawl the actual content of workbooks/data sources.
Tableau is both an online and on-prem version and the Glean-Tableau integration has been engineered to work with both right out of the box.
Glean uses the Tableau Server REST API to ingest all data:
Glean begins by understanding the users who are a part of the Tableau instance and their associated roles and permissions in the system.
Glean crawls all workbooks and data sources in the customer’s Tableau instance using the admin credentials granted in the initial authentication flow.
For each individually authenticated user, Glean performs additional processing to understand which users should be allowed to see each workbook and data source.
Those access policies are then enforced so there is parity between permissions for Tableau content in Glean and the original permissions in Tableau.
Glean performs a full crawl of the content monthly and makes use of incremental crawls to update existing content and permissions several times every hour.
A Tableau admin is required to go through the initial authentication flow to connect Glean with Tableau. The initial authentication flow provides Glean credentials with which to access the Tableau Server REST API on behalf of the customer.
Instructions are provided onscreen in the deployment console, but a summary is also provided here:
Determine the domain and site content URL of your Tableau instance:
Generate a Personal Access Token (PAT):
Users who want to start accessing Tableau search results in Glean need to authenticate individually by following these steps:
Glean allows configuring for only a certain user set to have access to Tableau search results.
For any questions or issues with this setup, please reach out to support@glean.com.