Publishing, Sharing, and Your Capstone Dashboard

Your dashboard is finished. It is clear, it answers the question people kept asking, and it sits on your laptop where nobody else can reach it. So you do what most people do. You export a picture, paste it into an email, and send it to the team. By Thursday the numbers are stale, three people are looking at three different versions, and someone asks you to “just resend the latest one.” You have built a great dashboard and turned yourself into a delivery service.

This chapter fixes that. Publishing puts your work in one place, live and current, where the right people can open it in a browser and always see today’s numbers. No exports. No attachments. No version confusion. This is the last step of the Tableau workflow, and it is the step that turns a file you made into a tool your team uses.

Why this matters

A dashboard that lives on one computer helps one person. The moment your work matters to a team, the question stops being “how do I build this” and becomes “how do everyone else see it, safely, and stay current.” That is a different skill, and it is the difference between a personal project and something a business actually runs on.

Publishing also protects you. When there is one official dashboard that refreshes on its own, there is no arguing about whose spreadsheet is right. The finance lead, the regional manager, and your boss all open the same link and see the same truth. You stop being the bottleneck who re-runs the report, and you start being the person who built the thing everyone relies on.

Before we go further, one vocabulary check. A workbook is the Tableau file that holds your views, dashboards, and its connection to the data. Publishing means uploading that workbook to a Tableau site on the web so other people can open it. That site can be one of three things, and choosing the right one is where we start.

Tableau gives you three homes for a published workbook. They differ in who hosts them, who can see them, and what they cost.

Tableau Public is a free cloud service run by Tableau. You save your workbook to it, and it lives on the open web. Anyone with the link can view it. This is wonderful for learning, for building a portfolio you can show an employer, or for sharing analysis of public data. It has one hard limit you must respect: everything you put there is public.

Tableau Cloud is Tableau’s paid, private hosting. Tableau runs the servers; your workbooks live in a private site only your invited people can reach. This is the common choice for a business that wants sharing without running its own infrastructure.

Tableau Server is the same idea as Cloud, except your own organization installs and runs it on its own machines. Large companies with strict security or data-residency rules often prefer this, because the whole system sits inside their own walls.

Here is the simple way to remember it:

Tableau Public  ->  free, hosted by Tableau, visible to ANYONE
Tableau Cloud   ->  paid, hosted by Tableau, private to your team
Tableau Server  ->  paid, hosted by YOUR company, private to your team

For learning and for the capstone at the end of this chapter, Tableau Public is all you need. For real work with real customer data, you will almost always use Cloud or Server.

How to publish a workbook

Publishing follows the same shape everywhere. You open the publish command, pick where it goes, name it, and confirm what travels with it.

To publish to Cloud or Server, you open the Server menu in Tableau, choose Publish Workbook, and sign in to your site. Tableau asks for a name, a project (a folder on the site), and who is allowed to see it. When you publish, you also choose how the data comes along: your workbook can carry its own copy of the data, or it can point at a shared data source that other people already use.

Publishing to Tableau Public is even simpler, and it is free, so it is where you will practice.

Try It Publish your first workbook to the open web.

Open a workbook you built in an earlier chapter. If you do not have a Tableau Public account yet, create a free one at the Tableau Public site first.

In Tableau, open the Server menu, hover over Tableau Public, and choose Save to Tableau Public.

Sign in with your free Tableau Public account when prompted.

Give the workbook a clear name, such as “Regional Sales Overview,” and confirm.

Tableau uploads it and opens the published version in your web browser. Copy that link and open it in a private browser window to see exactly what a stranger would see.

What did you notice? The link works for anyone, and the underlying data is visible too. That is the whole point of Public, and also its one big warning, which we come back to below.

Who can see and touch it: permissions and roles

Once a workbook is on Cloud or Server, two separate questions decide what each person can do. The first is permissions: for this specific workbook or folder, can this person view it, edit it, or download it? You set permissions when you publish and can change them later. A common setup is to let one team edit and let everyone else only view.

The second question is the person’s license role, which is the seat your organization pays for. Tableau has three, and in plain terms they stack like this:

A Creator is a builder. Creators get the full toolkit, including Tableau Desktop and Tableau Prep, and can connect to new data, build workbooks from scratch, and publish them. This is the seat you have been using through this course.
An Explorer interacts and edits lightly. Explorers open published dashboards, filter and dig into them, and can make small edits to existing content in the browser, but they do not connect fresh raw data the way a Creator does.
A Viewer looks and interacts. Viewers open published dashboards, click the filters you built, and read the numbers. They cannot edit. This is the seat for the largest group of people, the audience who just needs to see the report.

Pricing changes often and varies by edition, so treat these as rough ranges, not quotes. As of July 2026, per user per month billed annually, a Viewer runs roughly $15 to $35, an Explorer roughly $42 to $70, and a Creator roughly $75 to $115, with the higher end reflecting the enterprise edition. Every deployment needs at least one Creator. Always confirm current numbers on Tableau’s pricing page before you budget.

The everyday takeaway is easy. You, the builder, are a Creator. The handful of people who help maintain reports are Explorers. The dozens or hundreds who just read them are Viewers, and they are the cheapest seat by far, which is exactly how it should be.

Keeping the data fresh

Publishing a dashboard is only half the promise. The other half is making sure it shows today’s numbers, not the numbers from the day you built it. How this works depends on how your workbook connects to its data.

A live connection asks the original data source for fresh numbers every time someone opens the view. If your database is always current, so is your dashboard. The cost is speed, because every click sends a new question back to that source.

An extract is a compressed snapshot of the data that Tableau saves alongside your workbook. Extracts are fast, because Tableau reads its own local copy instead of bothering the original source. The tradeoff is freshness: an extract is only as current as the last time you refreshed it.

That is where refresh schedules come in. When you publish a workbook that uses an extract, you can tell Tableau Cloud or Server to rebuild that snapshot on a timetable so nobody has to do it by hand. You can schedule a refresh hourly, daily, weekly, or monthly, at times you choose. Set a sales dashboard to refresh every morning at 6 a.m., and the team opens fresh numbers with their coffee, automatically, forever.

One more piece is worth knowing by name, even if you never set it up yourself. If your data lives on a private database inside your company’s own network, Tableau Cloud cannot reach it directly through the public internet. Tableau Bridge is a small piece of software that runs on a machine inside your network and acts as a secure relay, letting Tableau Cloud keep that private data fresh on a schedule. When someone in IT mentions Bridge, this is what they mean: the connector that keeps your locked-down data flowing to your cloud dashboards.

One warning about Tableau Public

Tableau Public is free, which makes it the obvious place to practice. It is also completely open, which makes it the wrong place for anything private. Everything you publish there, the dashboard and the data behind it, is visible to anyone who finds the link. By default a visitor can even download your underlying data.

So the rule is simple and absolute. Never publish real customer names, salaries, health records, sales figures your competitors should not see, or anything else confidential to Tableau Public. If the data is not fit for a stranger to read, it does not belong there. For anything private, use Tableau Cloud or Server, which keep your work behind a login. Practice on public or made-up data, ship real data privately.

Your capstone: build it end to end

Now you put the whole course together. This is a project brief, not a click-by-click lab. Use everything from Chapters 1 through 7 to carry one real question from raw data all the way to a published dashboard. Pick a dataset you actually care about: a spreadsheet of your team’s sales, a public dataset about a topic you like, or your own budget. Aim for something with at least a few hundred rows and a date, a category, and a number.

1. Connect to real data. Open Tableau and connect to your source, whether that is an Excel file, a CSV, or a database, the way you learned in the connecting chapter. Confirm the fields came in with the right data types: dates as dates, numbers as numbers.

2. Prepare and combine it. Clean what needs cleaning. Fix a mislabeled category, split a full name into two fields, or filter out the rows you do not need. If your story needs two tables, join or blend them so the data lands in one tidy shape.

3. Build clear views. Create two or three individual views that each answer one question. Maybe a bar chart of sales by region, a line chart of the trend over time, and a map if location matters. Keep each one focused on a single idea.

4. Assemble a dashboard. Bring those views together onto one dashboard. Arrange them so the eye starts at the headline number and moves naturally to the detail. Give it a title that states the point, not just the topic.

5. Add a calculated field. Create at least one calculated field that the raw data did not hand you: a profit margin, a year-over-year change, a “flag high value orders” test. This is the moment your dashboard says something the spreadsheet could not.

6. Add interactivity. Give your reader a way in. Add a filter for the dimension people most want to slice by, and add a parameter if a “what if” control would help, such as letting the reader set a sales target line. Make the dashboard something people can explore, not just stare at.

7. Publish and share appropriately. Publish the finished workbook. If your data is public or invented, save it to Tableau Public and share the link. If it is real and private, publish to Tableau Cloud or Server instead, set permissions so the right people can view it, and if it uses an extract, put it on a refresh schedule so it stays current. Then send the link, not a screenshot.

When you can hand someone that link and walk them through every choice you made, you have done the whole job of an analyst.

Common pitfalls

Sending screenshots instead of the link. A picture is stale the second you send it, and it cannot be filtered or explored. Once your work is published, share the link. Let people open the live dashboard and answer their own follow-up questions.

Publishing private data to Public. This is the mistake that ends careers, not just projects. Tableau Public is open to the world. Before you click save, ask whether a stranger reading this data would cause harm. If the answer is anything but a clear no, publish to Cloud or Server instead.

Forgetting the refresh schedule. An extract with no schedule freezes on the day you published it, and three weeks later someone makes a decision on month-old numbers. If your dashboard uses an extract, set a refresh schedule the same day you publish, and match its frequency to how often the data really changes.

Buying the wrong seats. Handing a Creator license to someone who only ever reads reports wastes money, and it happens constantly. Match the role to the need: Creators build, Explorers tinker, Viewers read. Most of your audience are Viewers.

A dashboard you cannot explain. If you cannot say where a number comes from or what a calculated field does, neither can anyone else. Before you publish, quiz yourself on every figure. If one number leaves you guessing, fix that before you share.

Your move

Do the capstone. Not a smaller version, the whole thing, start to finish, on data you actually care about. Connect, prepare, build views, assemble a dashboard, add a calculated field, add interactivity, and publish it. Give yourself an afternoon and treat it as the real thing, because it is the exact workflow a working analyst uses every week.

When you are done, use the checklist below to grade your own work. Every box you can honestly tick is a skill you now own.

Self-assessment checklist

Done	I can say that I…
☐	Connected to real data and confirmed the fields came in correctly
☐	Prepared the data: cleaned, shaped, and combined tables where needed
☐	Built clear individual views, each answering one question
☐	Assembled a focused dashboard with a title that states the point
☐	Created at least one calculated field the raw data did not provide
☐	Added interactivity with at least one filter or parameter
☐	Published and shared it in the right place, public or private, for the data
☐	Can explain every number and every calculation on the dashboard

If you can tick all eight, you have completed the Tableau track. You can take a business question, find the data behind it, shape it, visualize it, and put a live dashboard in front of the people who need it. That is the full loop, and it is a genuinely valuable skill.

Part of the Tableau track. Developed with AI assistance and reviewed by a human editor. Tableau changes often; menu names, features, and prices may have shifted since the “checked on” dates in this chapter. Verify anything critical against Tableau’s official documentation.