Tableau Server licensing is role-based and can be complex to optimise as your user base grows. Here is how the licensing model works, what each role includes, and the common mistakes that lead to overpaying or under-licensing.
The quick answer
Tableau Server licensing is role-based: you purchase a number of licences at each role level, and each user is assigned to a role. The three roles are Creator (full authoring capability), Explorer (can edit and publish within a site, cannot connect to new data sources), and Viewer (read-only dashboard consumption). Pricing: Creator approximately $70/user/month, Explorer $42/user/month, Viewer $15/user/month (list price; contracted enterprise pricing is lower).
The implication for licence optimisation: most organisations overprovision Creator licences (assigning Creator to users who only need Explorer or Viewer) and underprovision Viewer licences for broad internal distribution. Conducting a licence audit — comparing assigned roles against actual feature usage — typically identifies 15–30% cost reduction in organisations that have not actively managed their licence mix.
The three Tableau Server roles
### Creator
Creator is the highest-capability role. Creators can: connect to any data source (live connections and extracts), create and publish workbooks, create and publish data sources, build calculated fields and parameters, use all desktop authoring features. Creator licences include Tableau Desktop, Tableau Prep Builder, and a Tableau Server seat.
Creator is the appropriate role for: data engineers who publish certified data sources, BI developers who build and maintain dashboards, power users who need full authoring capability, and Tableau Prep users.
Creator pricing (list): approximately $70/user/month on annual subscription. Enterprise contract pricing varies.
### Explorer
Explorer is the mid-tier role. Explorers can: view dashboards and workbooks, edit workbooks on the web (Tableau's web editing environment), download and work with published data source connections, create new views from existing published data sources, and publish workbooks built on existing data sources. Explorers cannot connect to new data sources directly or use Tableau Desktop.
Explorer is the appropriate role for: analysts who need to build their own views from certified data sources, business users who do customised analysis on published data, report builders who work within existing data source connections but do not need to define new ones.
Explorer pricing (list): approximately $42/user/month on annual subscription.
### Viewer
Viewer is the consumption-only role. Viewers can: view published dashboards and workbooks, interact with filters and parameters on existing views, subscribe to views and receive email snapshots, comment on views (if commenting is enabled), and download images or PDFs of views. Viewers cannot edit or create content.
Viewer is the appropriate role for: dashboard consumers, executives viewing KPI reports, operational staff who need access to specific reports, and external stakeholders granted access to shared views.
Viewer pricing (list): approximately $15/user/month on annual subscription. The lowest-cost option for broad internal distribution.
Tableau Server Add-ons
Several optional add-ons extend Tableau Server functionality at additional cost:
**Data Management Add-on** — adds Tableau Prep Conductor (scheduled Prep flows), Tableau Catalog (automated data asset catalogue with lineage and impact analysis), and the Lineage and Impact Analysis features in the Metadata API. Required if you want to automate Prep flows on Server. Priced per Server deployment.
**Server Management Add-on** — adds the Resource Monitoring Tool (detailed server health monitoring, performance alerting, user activity tracking), enhanced admin views, and Tableau Services Manager improvements. Required for the level of infrastructure monitoring needed in enterprise Tableau Server deployments. Priced per Server deployment.
**Embedded Analytics** — Tableau has specific licensing terms for embedding dashboards in external applications (customer-facing applications, SaaS products). Embedded analytics requires either a Viewer licence per end user or a Core-based licence (capacity-based, not per-user) depending on the model. If you are embedding Tableau in an application, verify your licence terms — embedded use under a standard Server licence is a licence violation.
Core-based vs role-based licensing
Tableau Server originally offered Core-based licensing (purchase a number of CPU cores, unlimited users) alongside role-based licensing. Core-based licensing is still available in some enterprise contracts and is often more economical for organisations with very large user populations (hundreds or thousands of Viewer-level users).
Under core-based licensing, you purchase a number of server cores (minimum 8 cores for a production deployment). Users are unlimited on a core-based licence. The trade-off: core-based licensing is purchased upfront for a server capacity rather than scaling with user count. For organisations with 500+ Viewer-tier users, core-based licensing often provides better economics than per-user Viewer licences.
Core-based licensing is negotiated directly with Salesforce/Tableau. If your organisation has a large user population, raise this option in licence negotiations.
Common licensing mistakes
**Assigning Creator to everyone.** The default IT approach — give everyone the highest role level so no one is blocked — is the most expensive pattern. Conduct a usage audit: which users actually connected to new data sources? Which users only used web editing? Which users only viewed? Match roles to actual usage, not anticipated maximum usage.
**Not using Viewer licences for broad distribution.** Some organisations restrict Tableau access to a small group of Creator/Explorer users rather than distributing read-only access broadly. This limits the business value of the investment. Viewer licences at $15/user/month are cheap enough to distribute to most data-consuming employees.
**Not auditing licence utilisation.** Licences are purchased for users who leave the organisation, move to different roles, or stop using Tableau. Without quarterly licence audits using the Tableau Server admin views or the REST API, unused licences accumulate. A 100-user deployment that grew over three years may have 20–30 licences assigned to inactive users or users who moved teams.
**Misunderstanding Prep Conductor licensing.** Tableau Prep flows that run on a schedule (rather than manually in Prep Builder) require Prep Conductor, which requires the Data Management Add-on. Organisations that build automation workflows in Prep without this licence are in violation. If you are scheduling Prep flows, verify the Data Management Add-on is in place.
**Not planning for the Tableau Server end-of-life timeline.** Licence renewals should be evaluated in the context of Tableau Server's end-of-life direction — renewing a multi-year Server licence when Tableau Cloud is the go-forward platform may not be economical. For context on the EOL timeline, see Tableau Server end of life.
How to right-size your licence mix
Step 1: Run a user activity report from Tableau Server admin views (or the USERS, HISTORICAL_EVENTS, and VIEWS tables via the REST API/content API). For each user, identify: last login date, total view interactions, any workbook publishing activity, any data source creation activity.
Step 2: Map users to appropriate roles based on actual behaviour:
- Users who published data sources → Creator
- Users who published workbooks using existing data sources → Explorer
- Users who only viewed without editing → Viewer
- Users who have not logged in for 90+ days → candidates for licence release
Step 3: Review the result with your data team and business stakeholders. Some users who appear as Viewer-level based on history may need Explorer capability for upcoming projects. Right-size current reality while planning ahead for near-term requirements.
Step 4: Reconfigure licence assignments. In Tableau Server, change user role assignments in the admin interface or via the REST API for bulk changes.
Step 5: Establish quarterly licence reviews as a governance practice. Onboarding should include role assignment based on expected use; offboarding should include licence release.
Tableau Server vs Tableau Cloud licensing
Tableau Cloud has a similar role-based licensing structure (Creator, Explorer, Viewer) with comparable per-user pricing. For organisations evaluating the Server-to-Cloud migration, the licence cost comparison is roughly cost-neutral on a per-user basis — the Cloud economics advantage comes from eliminating Server infrastructure costs (hardware, OS maintenance, DBA overhead), not from lower per-user licence fees.
For organisations with core-based Server licences (unlimited users), migration to Cloud typically increases licence cost, as Cloud is exclusively user-based. This is a material cost factor in the migration decision for large user-base organisations.
For the full migration decision framework, see Tableau Server vs Tableau Cloud and for migration cost breakdown, see Tableau Cloud migration cost.
Our Tableau consulting practice manages licence optimisation as part of managed service engagements and as standalone licence audits. If you want to understand whether your current licence mix is optimal or are planning a renewal, book a free 30-minute audit.
A former Microsoft data architect audits your data foundation, identifies your top priorities, and sends you a written plan. Free. No pitch.
Book a Call →