Video summary

How to Set Up a Tableau Site | Tableau Online, Cloud and Server Explained

Main summary

Key takeaways

Educational

Main Ideas and Lessons (What the Video Is Trying to Teach)

The video teaches how to set up and administer a Tableau site for Tableau Cloud (formerly Tableau Online), covering licensing, site creation, governance, publishing workflows, and ongoing maintenance.

Key topics include:

  • Licensing and pricing
    • Organization-level “sites/instances”
    • User-level roles and capabilities
  • Installing/using Tableau Cloud Manager to create the site
  • Choosing the site location (including data residency considerations)
  • Understanding Tableau Cloud vs Tableau Server
    • Who owns/manages the servers
  • Logging into the site and taking an initial tour of the user experience
  • Administrator responsibilities: users, permissions, and groups
  • Publishing and maintaining dashboards/workbooks:
    • Publish
    • Replace/overwrite
    • Web editing
    • Refreshing data
  • Setting up governance early using templates and project/folder maturity levels

Methodology / Step-by-Step Instructions Presented

A) Decide Licensing for Tableau Cloud (Organization-Level and User-Level)

Organization contract / licensing tier (example guidance)

  • Start with Standard for smaller companies (e.g., ~100 people or less).
  • Use Enterprise for larger organizations (e.g., thousands of employees).
    • Enterprise provides more sites (example: 10), so departments can be separated (HR, Finance, Engineering, etc.) rather than mixed.
  • Use Tableau Plus for very large organizations (e.g., tens of thousands of employees).
    • Provides up to 50 sites
    • Requires contacting Tableau directly (not only via the self-service portal).
  • Recommendation: for larger organizations, talk to Tableau (not just self-service buying) so Tableau can tailor the setup.

User-level license types (roles/capabilities)

  • Creator (most expensive): design dashboards, connect to data, publish
  • Viewer (cheapest): log in and view dashboards/data (minimal capabilities)
  • Explorer (middle): interactive usage beyond Viewer, but not full Creator authoring

Practical note

  • Start with at least one Creator license.

B) Purchase the License

  • Use Tableau’s pricing/buy flow (the video recommends “Buy Now” to view individual components).
  • Choose the appropriate organization tier (example guidance: Standard for smaller companies).
  • Complete the online steps:
    • Enter details
    • Receive an invoice/paperwork email
    • Wait for provisioning
  • Wait for a provisioning email that includes/indicates Tableau Cloud Manager access.

C) Use Tableau Cloud Manager to Create the Site

  • Open the provisioning email and click Sign in to access Tableau Cloud Manager.
  • In Cloud Manager:
    • Create a new site using Create (the site starts empty).
    • Enter:
      • Site name (e.g., department name or company division)
      • Initial site administrator (initially you if only one Creator license exists)
      • Site URI (copy and save it—important for the admin login flow)
      • Site location (critical)
        • Choose a region/data residency location
        • Example mentioned: location matters for compliance/security (e.g., sensitive medical data)
        • Once selected, the site location cannot be changed.
  • Wait a few minutes for the site to finish creating.

D) Log into the Tableau Cloud / Tableau Online Site

  • Use the Cloud Manager + URI flow (admin access often requires the URI at an extra step).
  • General steps:
    • Go to the Tableau online login / SSO URL or the main Tableau Cloud sign-in page
    • Sign in with standard Tableau credentials
    • If you’re the site administrator, use the URI when prompted (Cloud Manager helps identify the correct site)

E) Understand Tableau Cloud vs Tableau Server (Ownership Model)

  • Tableau Cloud (Tableau Online)
    • Tableau owns and manages the servers
    • Benefits: less operational burden (no customer server outages/infra management)
  • Tableau Server
    • The customer controls/owns the servers
    • Tableau software is installed into the customer-managed environment
    • Needed when the organization requires full control over its own infrastructure for data/storage

F) Initial Tour: How People Use the Platform

For non-admin users, the focus is on Explore:

  • Users see folders/projects and dashboards published by creators.
  • The platform replaces email distribution with:
    • Self-service exploration (users filter/drill into views without waiting for emailed files)

Collaboration features mentioned:

  • Subscriptions: scheduled outputs delivered by email (PDF/image/text)
  • Comments:
    • Tag the designer
    • Attach a “snapshot” of the viewed state using a snapshot button

Collaboration goal:

  • Make sure designers understand the exact view/state a consumer questioned.

G) Administrator Workflow: Add Users and Manage Access

  1. In the admin interface, add users.
  2. Purchase additional licenses as needed:
    • Use “buy more licenses” / Cloud Manager for license expansion
    • The video notes you typically don’t manually re-assign licenses to the same deployment
  3. Manage access via permissions
    • Permissions control:
      • Publishing ability
      • Visibility to folders/dashboards/datasets
      • Downloading data
      • Whether users can perform certain actions
    • Purpose: enforce governance and prevent accidental deletion/misuse
  4. Use groups to scale permissions
    • Create groups such as “power users,” “designers,” “middle management”
    • Apply permissions to groups instead of setting them for each user
    • Users inherit permissions from their group

H) Publish Workbooks to Tableau Cloud (From Tableau Desktop)

Goal: publish a workbook/dashboard to the correct Tableau Cloud site.

High-level process:

  1. In Tableau Desktop, prepare the workbook (connected to data sources).
  2. Sign in to the Tableau destination from within Tableau Desktop.
    • Use “Server → Sign in” to connect to Tableau Cloud
    • For site admin, the authentication flow may require the URI
  3. Publish the workbook:
    • Choose the location (top-level folders/projects)
    • Provide the workbook name
    • Publish (Tableau handles permissions/authentication/data source details)
  4. Confirm in Tableau Cloud that the workbook appears in the selected folder.

I) Update/Refresh Dashboards in Tableau Cloud

Updating workbook content/layout

  • Make changes in Tableau Desktop and publish again using the same workbook name.
  • Tableau prompts because the name already exists:
    • choose overwrite/replace when prompted.

Web editing (optional alternative)

  • Edit in the browser and refresh to reflect changes
  • The speaker references a “thumbs up” workflow.

Refreshing the data source

  • In Tableau Desktop:
    • Use Replace Data Source with the new file/data connection
    • Replace while preserving dependent dashboards/sheets
  • Then republish.

More complex refresh scenarios

  • If using systems like SQL Server, Oracle, or Google BigQuery, workflows can be more complex (not fully covered in the video).

J) Governance Setup: How to Prevent Chaos Early

The video emphasizes establishing governance early, because once many people publish, it becomes difficult to control changes (“once the horse is out of the barn”).

Two key governance components:

1) Dashboard/template standards for creators

Example template elements:

  • Title
  • Author/creator credit
  • Contact/email (designer identity)
  • Last updated information (data refresh date)
  • Basic versioning
  • Optional formatting conventions (colors/styles)

Effect:

  • New creators copy expected patterns
  • Stakeholders know what to expect and where to look

2) Project/folder maturity stages (“quality gates”)

Folders represent maturity stages such as:

  • Sandbox → Review → Verified → Certified (names can vary)

Purpose:

  • Start with exploratory builds (e.g., local CSV/extracts)
  • Promote solutions upward as they become:
    • more accurate
    • better documented
    • more trusted

Gate intensity increases with each stage:

  • Review: basic checks by colleagues
  • Verified: possibly include data engineers/panels
  • Certified: approvals by stakeholders/high-position reviewers
  • Potential extra requirements at the top:
    • Documentation (data dictionary, governance notes)
    • Backups/local copies
    • Locked rules/data models

Caution:

  • Don’t make governance so strict that everything stays in Sandbox; otherwise high-quality work never gets promoted.

Speakers / Sources Featured

  • Speaker/Source: The video creator (referred to as “guys, welcome back”)
    • Mentions having a website called Jellyman Education
    • Mentions a named dashboard designer example: “Jed”
  • No other distinct person or separate organization is presented as a separate speaker in the subtitles.

Original video