The five biggest challenges teams face when sharing Tableau dashboards with external clients, and how a purpose-built reporting portal solves all of them.
Before diving into solutions, it helps to understand exactly why sharing Tableau dashboards with external audiences is so difficult. If you have tried to share dashboards with people outside your organization, you have probably run into at least a few of these.
Tableau offers two pricing approaches for giving external users access to dashboards. The first is user-based licensing, where each viewer gets a named Viewer seat. The second is usage-based pricing, where you pay based on dashboard impressions rather than individual users. Both models have their place, and the right choice depends on how your external audience actually uses your dashboards - how many people, how often, and how many views they generate.
The challenge is that choosing the wrong model for your audience's usage patterns can be costly. User-based pricing makes sense when you have a smaller number of heavy users who check dashboards frequently. Usage-based pricing can be more economical for large audiences who check in occasionally. But if you guess wrong - or if your usage patterns shift as your client base grows - you can end up significantly overpaying.
Row-level security (RLS) is the mechanism that ensures Client A only sees their own data and never sees Client B's. Tableau supports RLS natively, but making it work for external audiences typically means configuring it in two places: inside Tableau itself and inside whatever application layer sits between Tableau and the end user.
This dual-configuration approach is fragile. A misconfigured filter, a missing user mapping, or a testing gap can expose confidential data to the wrong audience. For organizations in regulated industries, this is not just an inconvenience - it is a compliance risk.
When you share a Tableau dashboard, your client sees Tableau. They see the Tableau toolbar, the Tableau navigation, and the Tableau visual style. Your company's logo, color scheme, and identity are nowhere to be found. For external reporting, this undermines the professional experience you are trying to create.
The most common ways to get Tableau content to external audiences all have significant drawbacks. Tableau Public makes everything visible to anyone on the internet. Email subscriptions send static PDF snapshots that go unread. Sharing Tableau Server links requires each viewer to have credentials and a license.
Every time you add a new external client, someone has to provision a Tableau account, configure row-level security filters, test that the client sees only their data, and communicate login credentials. This becomes a repetitive, manual process that scales poorly.
Tableau Public is free and easy, but it is designed for open data sharing, not private client reporting. Every dashboard is visible to anyone with the URL. If your data contains anything client-specific or confidential, Tableau Public is off the table.
Tableau gives you two paths here: named Viewer licenses or usage-based pricing per dashboard impression. Both are legitimate options, and for some organizations, one or the other is genuinely the most cost-effective route. The difficulty is that making this decision well requires a clear understanding of your audience's usage patterns. Beyond cost, you still face the same challenges around user management, branding, and user experience with relying on the standard Tableau log-in experience and content management options
The Tableau Embedding API gives you the tools to build a custom web application with your own authentication and branding layer on top. This is the most flexible option, but it is also the most resource-intensive. You need developers, a security review, and an ongoing maintenance commitment.
A reporting portal sits between your Tableau deployment and your external audience. It handles authentication, row-level security, branding, and the user interface. Your clients log into the portal - and the portal has a trusted authentication into Tableau. They see your brand, your dashboards, and only their data.
A portal product works alongside Tableau's licensing, and the right portal vendor will help you navigate the decision between user-based and usage-based pricing based on your specific audience. The Portal Panda team has worked with dozens of customers to identify the most cost-effective Tableau licensing approach for their deployment.
Row-level security is configured once in Tableau and portal and enforced automatically. The secure JSON web token approach doesn't allow for filter misconfiguration to expose the wrong data.
The portal carries your logo, your colors, your domain, and your UI. To your clients, it looks like a product you built with no Tableau branding to be seen.
Instead of emailing static PDFs, you give clients a login to a polished portal where they can access their dashboards anytime.
Adding a new client takes minutes. Configure their data access, send an invitation, and they are live.
Portal Panda gives your external clients a secure, white-labeled interface to access Tableau dashboards — with zero custom code.
Book a Demo