Skip to content
NewNeenOpal Earns ISO 42001 Certification for AI GovernanceKnow More

Tableau Embedded Analytics Services for Secure Multi-Tenant SaaS

NeenOpal is a certified Tableau Partner delivering Tableau embedded analytics for SaaS products, customer portals, and internal apps. We embed Tableau dashboards using Connected Apps and JWT SSO, with row-level security enforced inside Tableau itself, so every tenant sees only their own data without logging into a second product.

Architecture

Our Tableau Embedded Architecture: Connected Apps & JWT SSO

Connected Apps is Tableau's recommended method for securing embedded dashboards. It replaces the older trusted-ticket approach many legacy Tableau Server embeds still use. A trusted ticket confirms only who the user is. A Connected App sends a signed token (JWT) that also carries the user's permissions and data access, all in one step.

The token is created and signed on your servers, so the secret key never reaches the browser. If anyone alters it, the signature fails, and Tableau rejects the request. Here's how the process works:

  • 01

    Establish trust (one time)

    A Tableau Cloud admin creates a Connected App using direct trust, which provides a Client ID, Secret ID, and Secret Value. These let Tableau recognise tokens that genuinely come from your application, and embedding can be limited to approved domains.

  • 02

    Your server signs a JWT

    When a logged-in user opens an embedded view, your backend creates a short-lived JWT that names the Tableau user and can carry attributes such as tenant ID or role. It's signed with the Secret Value, which never leaves your server.

  • 03

    Tableau verifies

    Tableau checks the token's signature, expiry, audience, and scopes, and confirms the user exists on the site. If anything doesn't match, the request is rejected, so a forged or expired token never reaches a dashboard.

  • 04

    Dashboard loads

    The user goes straight into the embedded dashboard with no separate Tableau login. Their Tableau permissions control what they can open, and the token's attributes can drive row-level security where content is built to use them.

In production

A Real Embedded Analytics Rollout

A client had built an internal portal as the hub for their operations, with tools, reports, and data in one place. Moving to Tableau Cloud broke it: users were redirected out into Tableau Cloud separately, so they could no longer compare dashboards against the other data on the same screen.

We embedded the Tableau dashboards directly into the portal with Connected Apps and JWT. Users now see live interactive dashboards inside the portal, compare them against adjacent data, and never leave or log in to Tableau separately. Adoption rose because the analytics became part of the natural workflow rather than a separate tool.

Tableau dashboards embedded inside a customer portal

Outcomes

Outcomes Enterprise Leaders Measure Us By

Financial Impact Delivered to Clients
$750M+
Of engagements reached North Star outcomes within 90 days
85%
Average cloud cost savings across client operations
60%
Tableau dashboards delivered by 30+ certified Tableau experts
900+

Use cases

Where Clients Embed Tableau

Embedding fits wherever your users already work, each one secured differently, but never with a second login.

  • Customer Portal

    A client-facing site where end customers log in to see only their own data, like a logistics firm showing each client its shipment analytics. Every customer sees their own slice via Connected Apps + JWT.

  • Internal Business App

    An intranet or internal tool where employees use live dashboards every day without ever knowing Tableau powers them. Connected Apps handles seamless SSO, so no one needs a separate login to get in.

  • Client Reporting Portal

    Common in consultancies and agencies, where the deliverable is a live interactive dashboard, not a static report. Clients log into a branded portal and see only their own data slice, every time.

Licensing

Tableau Embedded Analytics Licensing: Where Most Teams Get Caught Out

The model you choose here shapes both your bill and how the deployment gets architected, so it's worth getting right before you build. Here's how the two options work:

ModelHow it worksBest for
Named User (Per Seat)
$15 /user/month
Each external user needs their own Viewer license. Internal users are covered under standard named seats.Small, identifiable sets of external users.
Usage-Based (Analytical Impressions)
No cap on viewer accounts
Pay for a pool of impressions: one is consumed each time a viewer loads a dashboard, exports content, or receives a subscription.Large external deployments, such as customer portals and SaaS products with hundreds or thousands of users.

Two things most clients miss

  • Standard Tableau Cloud Viewer/Explorer seats do NOT cover external users accessing embedded content. External users require the Embedded Analytics license, or you are outside Tableau's EULA.
  • The Embedded Analytics license cannot run in the same Tableau environment as your existing full-use licenses. They must be on separate sites, which significantly changes how the deployment is planned and architected.

At scale

Tableau Embedded Analytics at Scale: How We Handle It

A handful of embedded users is simple. Hundreds or thousands of external customers is an architecture question, and the parts that break first are entitlements, licensing, and site design.

  • Entitlement tables replace hand-built filters

    At scale, hand-maintained user filters stop holding up, so we drive row-level security from an entitlement table joined at the data layer. Onboarding a new customer means one data update, scaling security without hand-configuring each user.

  • Usage-Based licensing past a threshold

    Beyond a certain viewer count, per-seat Named User licensing stops making sense; Usage-Based (Analytical Impressions) is the model built for large external audiences who can’t each hold a seat.

  • A dedicated embedded site

    Because the Embedded Analytics license can't share a site with full-use licenses, external customers are served from their own site, which also cleanly separates their governance and content from internal users.

  • Isolation you can prove

    Identity and entitlements are enforced inside Tableau from the signed token and the entitlement join. Scale never loosens isolation; one customer can never see another's rows, regardless of viewer count.

Case studies

Related Case Studies

Client reviews

What clients say about working with us

Each member of the team is interested and knowledgeable about the process!

NeenOpal Intelligent Solutions is understanding and invests heavily in the project at hand. The engagement resulted in an optimized inventory and increased sales, meeting the expectations of our internal team!

Kapila PereraIT DirectorSinger Sri Lanka PLCVerified review on Clutch

They are attentive to detail and have shown us they can solve difficult problems.

We’re excited to partner with NeenOpal for their collaborative approach, on-time delivery, clear communication, and attention to detail. Their ability to solve complex problems, paired with creative design and forward thinking, sets them apart.

Joyce Ann McGinnFounder & COOCompris, Inc.Verified review on Clutch

I like that the team is incredibly hard-working, talented, and good with people.

NeenOpal is a hard-working, talented team that consistently brings fresh ideas. Their domain experience reshaped our MIS reporting and delivered deeper insights, helping us approach complex business challenges with greater clarity and improved resource productivity.

Saransh ChaudharyCEOVenus Remedies LimitedVerified review on Clutch

NeenOpal delivers high-accuracy analytics that drive reliable, KPI-driven outcomes.

It’s been a pleasure working with NeenOpal from the outset. They delivered our data lake on time and consistently demonstrate high numerical accuracy and strong analytical expertise. By meeting key KPIs, they support smooth operations and measurable business outcomes.

Saurabh BholaCTOThe Healthy Mummy Pvt. Ltd.Verified review on Clutch

Embed Tableau in your product

Tell us about your product, your tenants and who needs to see what. A certified Tableau consultant will follow up with next steps.

FAQ

Tableau Embedded Analytics FAQs

Direct answers to the concerns that matter before committing time and budget.

How do you secure multi-tenant Tableau embedding?

Connected Apps with signed JWT tokens carrying user attributes; Tableau filters each user's data slice server-side, so every tenant is served securely from the same dashboard.

Does row-level security work if someone edits the embed URL?

Yes. Row-level security is enforced inside Tableau, not just on your website, so manipulating the embed URL cannot expose data a user isn't permitted to see.

How are embedded external viewers licensed?

Either as Named Users ($15/user/month, each with a Viewer license) or usage-based Analytical Impressions with no cap on viewer accounts, which suits large external deployments.

Can I use my existing Tableau licenses for embedded external users?

No. External embedded access requires the Embedded Analytics license, and it must run on a separate site from your existing full-use licenses. Standard Viewer/Explorer seats leave you outside Tableau's EULA.

Do embedded users need a separate Tableau login?

No. Connected Apps provides seamless SSO, so users drop straight into the embedded dashboard with no separate Tableau login.

Where can Tableau be embedded?

In SaaS products, customer portals, internal business apps and branded client reporting portals, wherever your users already work day to day.