Tableau Next for ISVs, How to Ship Analytics Inside a Managed Package

Since April 2026, Salesforce ISV partners can build, package and embed Tableau Next analytics in the apps they sell. The packaging path is not the Apex path. Your dashboards and visualizations go into a Data 360 data kit, your managed package points at that data kit, and Salesforce recommends app templates to install the assets in each customer's org. Every customer user who opens them needs a Tableau Next license and permission set in their own org.

For a SaaS company with a Salesforce app, that decides whether Tableau Next belongs in your package at all. It pays off when your customers already run Data 360 and Tableau Next, and it adds a prerequisite to every install when they don't. Appnigma's marketplace apps team builds native Salesforce apps for SaaS companies and covers "a native app, marketplace listing preparation, and review support." If you are a Salesforce admin who wants to know what Tableau Next is, start with Tableau's product page instead.

Updated October 2026. Checked against Salesforce's Tableau Next ISV developer guide, the App Template Framework guide and the packageable components tables. This update corrects the earlier version of this post, which said Tableau views are declared in sfdx-project.json and packaged like Apex, that 1GP packages can't hold Tableau Next components, and quoted a security review fee and revenue share that official pages don't support. It adds the data kit workflow, the install steps in the customer org, the license picture and the Embedding SDK route.

What changed for ISVs in April 2026

Tableau Next itself isn't new. Salesforce announced in April 2025 that "Tableau Next is now generally available with the Tableau+ SKU" (Salesforce News). What arrived a year later is the partner route. The Summer '26 ISV strategy post lists "Tableau Next for ISVs" as generally available in April 2026, and says "you can build, package, and embed interactive analytics."

In practice that gives you four things to ship. Packaged assets are the main one. These are dashboards, visualizations and metrics, along with the workspaces and semantic models behind them, installed into the customer's org. Dashboard extensions are custom Lightning Web Components with the analytics__Dashboard target, which appear in the Tableau Next extension picker (LWC extensions guide). The Embedding SDK renders those assets in your own web app. And the hosted Tableau Next MCP server lets an outside AI agent query the customer's semantic layer.

The last row comes from Salesforce's billing considerations, which say the MCP server tools "consume Flex Credits as prompts."

Should your app ship Tableau Next assets?

Tableau Next runs on Data 360. Salesforce's ISV guide says it "is built on top of Data 360" (Get Started), and the App Template Framework requires that the org "must have Data 360, Semantic Layer, and Tableau Next enabled" (ATF get started). So the real question is whether your customers' data and licenses are already there.

Three signals say yes. Your buyers are on Salesforce editions that include Tableau Next, which Salesforce says covers "Core, Advanced, and Max Editions" (Tableau Next page). Your product's data can land in Data 360 through data streams you ship in the data kit. And your customers ask analytical questions across your data and their CRM data, the kind a semantic model and an agent answer better than a list view.

If your buyers are on older editions or haven't turned on Data 360, the prerequisite becomes part of every sale. Lightning reports and dashboards over your custom objects need nothing extra and install with any managed package. CRM Analytics templates are still packageable as a WaveTemplateBundle in both 1GP and 2GP (2GP components table), and Salesforce says CRM Analytics "will continue to exist for customers who are not ready for that journey." A sensible pattern is to keep standard reports in the core package and offer Tableau Next assets to the accounts that have it.

How packaging works, from data kit to managed package

The setup starts on the partner side, and it takes a support case. Salesforce's scratch org workflow says "Data 360 scratch org support is only available when the Dev Hub is part of your Partner Business Org (PBO)," and partners "must log a case in the Salesforce Partner Community" to get it. You also enable 2GP in that Dev Hub and register a namespace. Our guide to registering a package namespace covers that step.

Your scratch org definition then turns on Data 360 and Tableau Next. This is the feature list from Salesforce's sample file.

{
  "orgName": "Salesforce",
  "edition": "Developer",
  "features": ["EnableSetPasswordInApi", "CustomerDataPlatform", "CustomerDataPlatformLite", "TableauEinstein"],
  "settings": {
    "customerDataPlatformSettings": { "enableCustomerDataPlatform": true }
  }
}

After you enable Tableau Next in Setup and build your assets, the unit you package is the data kit, not the individual dashboard. The data kit workflow has you add your Data 360 elements to a standard data kit, click Download Manifest, and retrieve the metadata into your Salesforce DX project with sf project retrieve start --manifest package.xml. Then you create the package against the data kit folder.

sf package create -n PACKAGE_NAME -t Managed -v DEVHUB_ALIAS -p PATH_TO_DATA_KIT
sf package version create -v DEVHUB_ALIAS -k INSTALLATION_KEY -p 0ho_ID -w 45 -f config/project-scratch-def.json

Both commands come from Salesforce's Package Your Tableau Next App page. It notes that "beta packages can only be installed in scratch orgs," so you promote the version before any customer can install it. sfdx-project.json only changes if your app builds on the Data Cloud SSOT package. In that case you declare the SSOT package as a dependency, and its ID is on the Partner Community site.

The data kit workflow suits a team, because the retrieved project goes into source control and another developer can deploy it to their own scratch org and add a data stream. That is the same branch-and-merge habit you already use for Apex, applied to Data 360 metadata.

Can you package Tableau Next in 1GP?

The packageable components tables don't support a blanket "2GP only" rule. The 2GP table lists AnalyticsVisualization and AnalyticsWorkspace as "Packageable In: First-Generation Managed Packages (1GP)." AnalyticsDashboard appears only in the 1GP table. The two components that carry a Tableau Next app, AppFrameworkTemplateBundle and DataPackageKitDefinition, are listed for both 2GP and 1GP.

Our reading is that in 2GP the individual assets travel inside the template rather than as standalone components. That is an inference from the tables, and Salesforce doesn't state it in those words.

What Salesforce prescribes for partners is 2GP. The data kit workflow says a Tableau Next templated app is packaged much like "any app with second-generation packaging (2GP)," and the scratch org prerequisites start with enabling 2GP. If you are still on 1GP, the tables suggest your existing package can hold these types, but every Tableau Next step in the ISV guide assumes a 2GP project. Our guide to moving a 1GP package to 2GP covers that move.

What happens in the customer's org after install

Installing the package doesn't put a working dashboard in front of users by itself. The 2GP table says "Data Cloud and Tableau Next assets are installed in subscriber orgs via templates using the AppFrameworkTemplateBundle." Salesforce's own advice on the Deploy Tableau Next Assets page is "We recommend building templates to deploy your Tableau Next and Data 360 solutions to your production orgs and your customers."

So a customer install has two phases. First the managed package installs. Then an app is created from your template, and the App Template Framework runs what it calls org readiness checks, prerequisite actions and a guided installation wizard. Your template can check the org before creating anything. The TemplateRequirementEvaluation node exists to "evaluate template requirements in the org before the app is created," and the DataKitInstall node deploys your data kit into a data space and polls until the job finishes, for up to 30 minutes (DataKitInstall).

That second phase is where support tickets come from. The person running it needs the Tableau Included App Manager permission set, which the 2GP table lists as the license requirement for the template bundle, plus Data 360 access. After deployment, the Packages and Data Kits guide says "Subscribers can add components but can't modify or delete any deployed mappings or components." Write your install guide around both facts, and build a readiness check for anything your dashboards assume, like a minimum row count in a data model object.

Who pays for the licenses and credits?

The customer does, through licenses in their own org. Salesforce's permission sets and licenses page says "Each user that interacts with Tableau Next requires a license and a permission set." The Tableau Next pricing page lists plans starting at $40 per user per month, billed annually, and many customers already hold licenses through the editions that include Tableau Next.

The license types on that Help page map to different jobs in an ISV install.

Licenses aren't the whole bill. Salesforce describes Tableau Next pricing as role-based but adds that "Data Services Credits and/or Flex Credits costs may still apply" (Tableau Next page). If your data kit streams large volumes into Data 360 or your product calls the MCP server, that usage lands on the customer's credits. Say so on your listing, next to the Tableau Next prerequisite.

We found no official route for an ISV to bundle or resell Tableau Next licenses. Help lists a Tableau Next Included App license for "pre-packaged (templated) Tableau Next Apps for Salesforce," but it doesn't say partner apps qualify, so don't build pricing on it until your partner account manager confirms. The partner-side SKU Salesforce has announced is Data 360 Provisioning for ISVs, which the Summer '26 post says "replaces legacy Cloud SKUs."

For trials, decide early. A trial org without Tableau Next shows your core app and none of the analytics. You can gate the analytics module on the prerequisite or ship the template as a separate add-on that customers install once they have Tableau Next.

Embedding the dashboards in your own SaaS app

Some ISVs want the dashboards inside their own product, not inside Salesforce. The Embedding SDK does that, rendering Tableau Next dashboards, visualizations, metrics and the Tableau Agent in your web app. Two conditions shape the design. "The users for your web app must exist as users in your Salesforce org," and access comes "via a Tableau+ license or Tableau Next Creator license."

Authentication runs through an External Client App that produces a Frontdoor URL, which you pass as the SDK's authCredential (access token guide). The web server flow is the recommended one for interactive users, and Salesforce calls the JWT bearer flow "an alternative for non-interactive scenarios only" (JWT bearer guide). If your customers each have their own org, the SDK takes an orgConfigs map instead of one org URL. Check your version too. The overview says "Starting in July '26, you must use v2.0."

The user requirement is the design constraint. Embedding works when your app's users are already Salesforce users in the customer's org, like sales reps opening your product from a CRM workflow. It doesn't fit an audience of people who never log in to Salesforce.

Mistakes that delay an analytics app release

• Building in a Dev Hub that isn't your Partner Business Org. Data 360 scratch orgs are "only granted to PBO orgs," so the support case can't be approved for another org.
• Treating a second test org as free. Salesforce's development environments page says usage in a second production org is "metered, resulting in billing charges the same way it is on the production org."
• Packaging dashboards one by one instead of through the data kit and template, then finding the data streams and semantic models missing in the customer org.
• Writing install docs with old permission set names. The packageable components tables still say Tableau Next Admin or Analyst, while Help now maps those to Creator (Legacy) and Consumer (Legacy) licenses.
• Shipping an embedded integration on SDK v1.0 or v1.1, which stopped being supported in July 2026.
• Listing the app without stating the Data 360 and Tableau Next prerequisite, so customers install and find empty dashboards.

Frequently Asked Questions

Do customers need a Tableau Next license to use an ISV's dashboards?

Yes. Each user who views Tableau Next content needs a license and a permission set in the customer's org, and many customers get licenses through Core, Advanced or Max editions.

Can you put Tableau Next dashboards in a managed package?

Yes, through a Data 360 data kit and an app template. Salesforce's ISV guide packages the data kit folder with sf package create and installs the assets with App Template Framework templates.

Does Tableau Next ISV packaging require 2GP?

Salesforce's ISV workflow is built on 2GP. The packageable components tables still list the template bundle and data kit for 1GP too, so it isn't a hard platform block.

Can Appnigma build a Salesforce app that includes Tableau Next analytics?

Appnigma's marketplace apps service builds native Salesforce apps for SaaS companies, with "marketplace listing preparation, and review support." We can scope whether Tableau Next assets fit your customers before you commit to the data kit work.

About the author

Sunny Chauhan is the co-founder and CEO of Appnigma AI, which builds and maintains customer integrations and native Salesforce and HubSpot apps for B2B SaaS teams. Before Appnigma, he was on Salesforce's AppExchange team, where he worked with more than 300 SaaS partners. He has spent close to a decade on the Salesforce platform, including work at Zennify, and holds Salesforce certifications including Platform Developer II, Platform App Builder, Administrator, Data Cloud Consultant, and AI Associate.

Related Articles

• Data 360 Provisioning for ISVs and Flex Credits
• 1GP to 2GP Managed Package Migration
• Building Agentforce Components for AgentExchange
• How ISVs Can Embed Agentforce 360 in Their Products
• What Is Salesforce AgentExchange
• What the Salesforce Security Review Checks

Sources

1. Salesforce, ISV Strategy for the Summer '26 Release
2. Salesforce News, Tableau Next Is Generally Available
3. Salesforce Developers, Tableau Next ISV Guide, Workflow for Tableau Next Scratch Orgs
4. Salesforce Developers, Workflow for Creating Data 360 Data Kits with Tableau Next Assets
5. Salesforce Developers, Package Your Tableau Next App
6. Salesforce Developers, Deploy Tableau Next Assets
7. Salesforce Developers, App Template Framework Overview
8. Salesforce Developers, Components Available in Second-Generation Managed Packages
9. Salesforce Developers, Components Available in First-Generation Managed Packages
10. Salesforce Help, Tableau Next Permission Sets and Licenses
11. Salesforce, Tableau Next Pricing
12. Salesforce Developers, Get Started with the Tableau Next Embedding SDK
13. Salesforce Developers, Tableau Next MCP Server