AI in Tableau and Trust
It’s important that your data stays safe while you innovate with new technology. With AI in Tableau, we keep Trust as the #1 value, and we strive to make sure your data is secure while also creating experiences that are accurate and safe.
Starting in version 2025.3, you’ll be able to use Tableau Agent in Tableau Server. Tableau Agent in Tableau Server requires you to connect to your own Large Language Model (LLM) provider such as OpenAI. When you use your own OpenAI LLM provider, your requests won't go through the Einstein Trust Layer or use Salesforce’s Large Language Model (LLM) provider agreements. All data handling, including PII protection, is governed by your own provider and any provisions you have set up. For more information, see Turn on AI in Your Tableau Server Site.(Link opens in a new window)
The content in this topic primarily focuses on using AI in Tableau features in Tableau Cloud. Any content related to using AI in Tableau features in Tableau Server is mentioned specifically.
AI in Tableau and your data
In Tableau Cloud, to keep your data secure, Salesforce has agreements in place with Large Language Model (LLM) providers, like Azure OpenAI. Organizations can leverage generative AI capabilities without their private data being used to train the LLM.
In Tableau Server, you will connect to OpenAI directly using your own API key. Ensure your own OpenAI agreement and related settings comply with your organization's data security policies.
Trusted generative AI
Applies to Tableau Cloud only
Salesforce’s Einstein generative AI solutions are designed, developed, and delivered based on five principles for trusted generative AI.
-
Accuracy: We prioritize accuracy, precision, and recall in our models, and we back our model outputs up with explanations and sources whenever possible. We recommend that a human check model output before sharing with end users.
-
Safety: We work to detect and mitigate bias, toxicity, and harmful outputs from models used in our products through industry-leading detection and mitigation techniques.
-
Transparency: We ensure that our models and features respect data provenance and are grounded in your data whenever possible.
-
Empowerment: We believe our products should augment people’s capabilities and make them more efficient and purposeful in their work.
-
Sustainability: We strive towards building right-sized models that prioritize accuracy and reduce our carbon footprint.
To learn more about trusted AI, see Salesforce Research: Trusted AI(Link opens in a new window)
AI in Tableau supported languages and locales
AI in Tableau features support English (en_US). Starting in version 2025.1 (February release) a subset of additional languages are supported for Tableau Agent and Tableau Pulse in the feature areas listed in this section. Currently, generative AI in Tableau Catalog supports only English (en_US).
-
Tableau Pulse Insight Summaries and better semantic matching for Ask Q&A
-
Tableau Pulse Discover Enhanced Q&A (2025.2 and later)
-
Tableau Agent in Tableau Prep Web Authoring
-
Tableau Agent in Tableau Prep Builder (2025.2 and later)
-
Tableau Agent Viz Authoring
-
Tableau Agent in Tableau Desktop
PII, data security, and multi-language support
PII support may vary depending on whether you use Tableau Agent in Tableau Cloud or Tableau Server.
Tableau Cloud
The Einstein Trust Layer is designed with regional and language-specific PII patterns in mind. AI in Tableau features when connected to Tableau Cloud inherit the Einstein Trust Layer and security controls for supported languages. Some languages may not fully support pattern-based data masking, toxicity detection, or audit and feedback data.
For more information about the data types supported and toxicity detection available by language, as well as the types of audit data collected for generative AI, see Einstein Trust Layer Region and Language Support(Link opens in a new window) and Generative AI Audit and Feedback Data(Link opens in a new window) in the Salesforce help.
Tableau Server (version 2025.3 and later)
AI in Tableau features when connected to Tableau Server don't go through the Einstein Trust Layer. Instead, your requests are sent directly to OpenAI. This includes PII masking for different languages. You're responsible for ensuring that their service and youragreement can effectively detect and protect PII across the languages that Tableau Agent supports.
For more information, see Turn on AI in our Tableau Server Site(Link opens in a new window).
Languages and locales by feature area
When using Tableau Agent in Tableau Cloud or Tableau Server (version 2025.3 and later), the language used in the generative AI response is based on the Language set in your My Account Settings. If the setting in your My Account Settings is set to Unspecified, the browser language setting is used instead.
When using Tableau Agent in Tableau Desktop and Tableau Prep Builder, the language used in the generative AI response is based on the language selected in the Help > Choose Language menu.
The following languages are currently supported.
Tableau Pulse Insight Summaries and Enhanced Q&A (Discover)
Note: Einstein Trust Layer masking supports 6 core languages; others may reduce response quality. Metric names stay in original language. Input language detection may vary in unsupported locales.
| Language | Code |
| Chinese (Simplified) | zh_CN |
| Chinese (Traditional) | zh_TW |
| Dutch | nl_NL |
| English (United Kingdom) | en_GB |
| English (United States) | en_US |
| French (Canada) | fr_CA |
| French (France) | fr_FR |
| German | de_DE |
| Italian | it_IT |
| Japanese | ja_JP |
| Korean | ko_KR |
| Portuguese (Brazil) | pt_BR |
| Spanish | es_ES |
| Swedish | sv_SE |
| Thai | th_TH |
Tableau Agent in Tableau Prep Web Authoring
Note: Pattern-based data masking and toxicity detection not currently supported for French (Canada), Korean, and Portuguese.
| Language | Code |
| Chinese (Simplified) Available starting in 2025.3 | zh_CN |
| Chinese (Traditional) Available starting in 2025.3 | zh_TW |
| Dutch (available starting in 2025.3) | nl_NL |
| English (United Kingdom) | en_GB |
| English (United States) | en_US |
| French (Canada) Available starting in 2025.2 | fr_CA |
| French (France) | fr_FR |
| German | de_DE |
| Italian | it_IT |
| Japanese | ja_JP |
| Korean (available starting in 2025.2) | ko_KR |
| Portuguese (Brazil) | pt_BR |
| Spanish | es_ES |
| Swedish (available starting in 2025.3) | sv_SE |
| Thai (available starting in 2025.3) | th_TH |
Tableau Agent in Tableau Prep Builder
Tableau Agent in Tableau Prep Builder is available starting in version 2025.2
Note: Pattern-based data masking and toxicity detection not currently supported for French (Canada), Korean, and Portuguese.
| Language | Code |
| Chinese (Simplified) Available starting in 2025.3 | zh_CN |
| Chinese (Traditional) Available starting in 2025.3 | zh_TW |
| Dutch (available starting in 2025.3) | nl_NL |
| English (United Kingdom) | en_GB |
| English (United States) | en_US |
| French (Canada) Available starting in 2025.2 | fr_CA |
| French (France) | fr_FR |
| German | de_DE |
| Italian | it_IT |
| Japanese | ja_JP |
| Korean (available starting in 2025.2) | ko_KR |
| Portuguese (Brazil) | pt_BR |
| Spanish | es_ES |
| Swedish (available starting in 2025.3) | sv_SE |
| Thai (available starting in 2025.3) | th_TH |
Tableau Agent Web Authoring
Note: Pattern-based data masking and toxicity detection not currently supported for French (Canada), Korean, and Portuguese.
| Language | Code |
| Chinese (Simplified) Available starting in 2025.3 | zh_CN |
| Chinese (Traditional) Available starting in 2025.3 | zh_TW |
| Dutch (available starting in 2025.3) | nl_NL |
| English (United Kingdom) | en_GB |
| English (United States) | en_US |
| French (Canada) Available starting in 2025.2 | fr_CA |
| French (France) | fr_FR |
| German | de_DE |
| Italian | it_IT |
| Japanese | ja_JP |
| Korean (available starting in 2025.2) | ko_KR |
| Portuguese (Brazil) | pt_BR |
| Spanish | es_ES |
| Swedish (available starting in 2025.3) | sv_SE |
| Thai (available starting in 2025.3) | th_TH |
Tableau Agent in Tableau Desktop
Note: Pattern-based data masking and toxicity detection not currently supported for French (Canada), Korean, and Portuguese.
| Language | Code |
| Chinese (Simplified) Available starting in 2025.3 | zh_CN |
| Chinese (Traditional) Available starting in 2025.3 | zh_TW |
| Dutch (available starting in 2025.3) | nl_NL |
| English (United Kingdom) | en_GB |
| English (United States) | en_US |
| French (Canada) Available starting in 2025.2 | fr_CA |
| French (France) | fr_FR |
| German | de_DE |
| Italian | it_IT |
| Japanese | ja_JP |
| Korean (available starting in 2025.2) | ko_KR |
| Portuguese (Brazil) | pt_BR |
| Spanish | es_ES |
| Swedish (available starting in 2025.3) | sv_SE |
| Thai (available starting in 2025.3) | th_TH |
LLM selection and Geo-aware LLM request routing
Applies to Tableau Cloud only
Tableau Agent and Tableau Pulse Enhanced Q&A (Discover) don't support the selection of a Salesforce-managed Large Language Model (LLM). Instead, the development team at Tableau tests and selects the best model to use, based on performance, accuracy, and cost.
The models used by Tableau Agent and Tableau Pulse Enhanced Q&A (Discover) support geo-aware routing through the Einstein generative AI platform. Proximity to the nearest Azure OpenAI instance is determined by the Data Cloud region for your connected Salesforce org. If a model isn’t available in your Data Cloud region, or if there isn't enough available capacity, then the requests are routed to the US, and never to Azure OpenAI directly.
For information about which specific LLM models are currently being used in your version of Tableau Agent and Enhanced Q&A contact your Tableau Account Executive. For more information about Geo-aware LLM request routing, see Geo-Aware LLM Request Routing on the Einstein Generative AI Platform(Link opens in a new window) and Routing for Geo Aware models(Link opens in a new window) in the Salesforce help.
The Einstein Trust Layer in action
Applies to Tableau Cloud only
AI in Tableau in Tableau Cloud is powered by Einstein AI and inherits the Einstein Trust Layer and security controls.
Tableau Pulse
Insight summaries are grounded using templated natural language insights and values calculated using deterministic statistical models. Tableau Pulse is also based on a metric layer that provides a bounded, safe space for insights to be detected. Tableau Pulse uses generative AI to enhance and synthesize the language of the insights generated by Tableau. The result is summarized insights in easy to understand language that the user can quickly engage with.
Better semantic matching for Ask Q&A enhances semantic matching for any language. Questions and insights text are sent to OpenAI as part of the process for calculating semantic matching. All calls to OpenAI go through the Einstein Trust Layer.
Enhanced Q&A (Discover) uses statistical algorithms to examine grouped metrics and surface insights that are relevant, interesting, and worth investigating. It uses generative AI to generate intuitive key insights, relevant visualizations, source references, and suggested follow-up questions. Because it is powered by AI in Tableau, you can ask questions in your own words to get answers in natural language about your data.
Enhanced Q&A (Discover) supports multilingual questions and responses, aligned with Tableau Cloud supported languages. Suggested questions, follow-up questions, and insight briefs adapt to the site’s language setting. Discover detects the input language as users ask questions and seamlessly returns LLM responses in that language—even if it differs from the site or data language. Metric names and filters always remain in their original, authored language for clarity and consistency.
Note: Einstein Trust Layer masking supports 6 core languages; others may reduce response quality. Metric names stay in original language. Input language detection may vary in unsupported locales.
Discover, through the Einstein Trust Layer, uses advanced pattern matching and machine learning techniques to detect sensitive data in prompts. Personally Identifiable Information (PII) such as names and email addresses are automatically masked using machine learning. For best results, consider structuring your data with clear entity identifiers and consistent field labels to minimize ambiguity and ensure accurate results when masking is applied.
Tableau Agent
Note: When it comes to handling your data, there are a few differences depending on if you're using Tableau Agent with Tableau Cloud, or with Tableau Server. For more information, see Tableau Agent in action in Tableau Server (version 2025.3 and later). Whichever connection you're using, the result from the LLM is a viz, a calculation, a Prep flow plan, or an asset description ready for you to review.
To enable Tableau Agent to return a viz, a calculation, flow cleaning and transform suggestions, or an asset description, we first need to ground Tableau Agent in your data.
When you launch Tableau Agent, we query the data source that you're connected to and create a summary that includes field metadata (field captions, field descriptions from comments in Tableau Desktop or from Tableau Catalog, data roles, and data types) and samples up to 1000 unique field values if the data type is string (text). This summary is sent to the Large Language Model (LLM) to create vector embeddings so that Tableau Agent can understand the context of your data. The summary creation happens within Tableau and the summary context data is forgotten by the LLM as soon as the vector embeddings are created.
When you type a question or request into the conversation pane, a combined prompt consisting of the user's input, metadata describing the current state of the viz (web authoring), or Tableau Prep flow, and historical context from the conversation pane flow through the Einstein Trust Layer to the LLM.
If you are using Tableau Agent in Tableau Cloud, the prompt flows through the Einstein Trust Layer to the LLM.
The Einstein Trust Layer can be used to mask Personally Identifying Information (PII) using pattern-based data masking before it is sent to the LLM. Using machine learning and pattern matching techniques, PII in prompts are replaced with generic tokens and then unmasked with original values in the response. For more information about PII masking see Einstein Trust Layer Region Language Support(Link opens in a new window) in the Salesforce help.
The response flows back through the Einstein Trust Layer to check for toxicity and unmask any masked data. Due to our zero data retention policies in place with our third-party LLM providers, any data sent to the LLM isn’t retained and is deleted after a response is sent back.
Techniques like this ensure our products adopt generative AI in a trusted manner. At the same time, your customer data isn’t used to train any global model.
Want to learn more about the Einstein Trust Layer? See Einstein Trust layer: Designed for Trust(Link opens in a new window) in the Salesforce help, or take the Einstein Trust Layer(Link opens in a new window) module on Salesforce Trailhead.
Tableau Agent in action in Tableau Server (version 2025.3 and later)
Note: Tableau Agent in Tableau Server is currently available for viz authoring and Tableau Prep data preparation features only.
If you're using Tableau Agent in Tableau Server, you'll be using your organization’s LLM provider such as OpenAI. In Tableau Server version 2025.3, OpenAI is the only supported LLM provider.
When you type a question or ask for something in the conversation pane, the prompt doesn’t use the Einstein Trust Layer. This means that Tableau's built-in features to hide personal information and manage data won't work. Instead, Tableau sends your user question and a small random sample of values per field to your OpenAI account.
You are responsible for any data protection or PII masking that occurs on your provider's side. Ensure your own LLM provider agreement and related settings follow your organization's data security policies.
Reviewing generative AI outputs
AI in Tableau is a tool that can help you quickly discover insights, make smarter business decisions, and be more productive. This technology isn’t a replacement for human judgment. You’re ultimately responsible for any LLM-generated outputs you incorporate into your data analysis and share with your users.
Whether it’s suggesting steps or generating calculations to use in a Tableau Prep flow, summarizing insights for metrics you follow, creating visualizations for you from your data, or drafting descriptions for your data assets, it’s important to always verify that the LLM output is accurate and appropriate.
Focus on the accuracy and safety of the content before you incorporate it into your flows, visualizations, and analysis.
-
Accuracy: Generative AI can sometimes “hallucinate”—fabricate output that isn’t grounded in fact or existing sources. Before you incorporate any suggestions, check to make sure that key details are correct. For example, is the proposed syntax for a calculation supported by Tableau?
-
Bias and Toxicity: Because AI is created by humans and trained on data created by humans, it can also contain bias against historically marginalized groups. Rarely, some outputs can contain harmful language. Check your outputs to make sure they’re appropriate for your users.
If the output doesn’t meet your standards or business needs, you don’t have to use it. Some features allow you to edit the response directly before applying it to your data, and you can also try starting over to generate another output. To help us improve the output, let us know what was wrong by using the thumbs up and thumbs down buttons where available and provide feedback.