Can Tableau Send Email Reports?

Can Tableau Send Email Reports?

Someone on your team asks the obvious question: can you just email me this dashboard every Monday morning?

It sounds like it should be a checkbox. In Tableau it is a checkbox, but only if your workbook lives in the right place, and what lands in the inbox is probably not what the person asking has in mind.

This guide covers what Tableau can actually send by email, the two mechanisms that do it, how to set each one up, and the specific limitations that catch teams out after they have already promised a weekly report to a stakeholder.

Can Tableau Send Email Reports? The Direct Answer

Yes. Tableau has two built-in email delivery mechanisms, and they solve different problems:

• Subscriptions send a snapshot of a view or a whole workbook on a schedule. This is the weekly-Monday-morning case.
• Data-driven alerts send an email when a number on a chart crosses a threshold you set. This is the tell-me-if-sales-drop-below-X case.

Both come with one hard requirement that is easy to miss: the workbook has to be published to Tableau Cloud or Tableau Server. Tableau Desktop on its own cannot email anything. It has no mail server and no scheduler, so there is nothing in Desktop to schedule against. If your work only exists as a .twbx file on your laptop, email delivery is not a setting you have failed to find — it is a feature that lives one tier up.

The second thing to be clear about is what arrives. A subscription email contains a PNG image, a PDF attachment, or both, plus a link back to the live view. It is a picture of your dashboard, not the dashboard. Nobody can filter it, drill into it, or pull the underlying rows out of it.

Ready to stop guessing which pages are worth your time? Get a free SEO audit and see exactly where your site stands in search.

How Tableau Subscriptions Actually Work

A subscription is a standing instruction attached to a view: on this schedule, render this thing and mail it to these people.

Where to find it

Open the view on your Tableau site, then select Watch > Subscriptions in the view toolbar. If you do not see the subscribe icon at all, that is not a permissions problem on your account — it usually means the server-wide email option has never been switched on. More on that below.

What you choose when you set one up

The subscription dialog is short, but almost every option in it has a consequence:

• Recipients. Tableau users or groups, who need View and Download Image/PDF permissions on the content or the email will not render for them. There is also a Subscribe me option if you own the workbook.
• View or entire workbook. Send just the sheet you are looking at, or every sheet in the workbook.
• Format. PNG image, PDF attachment, or both. For PDFs you also pick paper size and orientation.
• Subject and message. Both customisable, plus a Don't send if view is empty option that suppresses the email when the view returns no data.
• Frequency. Either When Data Refreshes or On Selected Schedule.

The group-membership trap

This one costs people real credibility. When you add a group to a subscription, Tableau expands it into individual users at the moment you create the subscription. It does not stay bound to the group.

So when a new analyst joins that group next month, they do not start receiving the report. Nobody gets an error. The report simply goes to the original list forever until someone notices the new person was never on it. If your team changes, you have to re-create the subscription. You also cannot subscribe a group set at all.

The filter trap

Filters you have applied in the browser are not included in the subscription. If you filtered to the EMEA region and then subscribed, the email arrives unfiltered.

The fix is to save your filtered state as a custom view first, then subscribe to that custom view instead of the original. Do this before you tell anyone the report is set up, because the unfiltered version looks plausible enough that it can run wrong for weeks.

Not sure if your content is actually working? Request a free SEO audit and get a clear picture of what to fix first.

How to Set Up a Tableau Email Report, Step by Step

Assuming email is already enabled on your site, here is the whole sequence.

1. Publish the workbook to Tableau Cloud or Tableau Server, then open the view from All Workbooks, All Views, or its project in the Explore section. Nothing below works from Desktop.
2. Apply your filters and save a custom view if the report needs to be scoped to a region, product line or date range.
3. Select Watch > Subscriptions on the view toolbar, then add recipients and check their permissions include Download Image/PDF.
4. Pick view or entire workbook, preferring a single view unless someone genuinely reads every sheet, and choose the format: PNG for something people glance at on a phone, PDF when it gets forwarded or filed.
5. Tick "Don't send if view is empty" if the view only contains rows when something needs attention. An alert that arrives blank every day gets filtered into a folder and ignored.
6. Set the frequency — When Data Refreshes if the point is freshness, On Selected Schedule if the point is predictability — and write a subject line that says what the report is. You cannot edit the message later without unsubscribing and starting over.
7. Click Subscribe, then use Run Now to test. The email should arrive within about ten minutes.

That last step is the one people skip. Run Now is the difference between knowing the report works and assuming it does.

What an Administrator Has to Enable First

If subscription options are missing from the interface, the cause is almost always upstream of you.

• SMTP and server event notifications must be configured before subscriptions can be enabled at all, and a TSM administrator must switch on the server-wide option that lets users receive email for subscribed views. Until that happens, the subscription options do not appear in the interface for anyone.
• Attachments are separately gated: the site has to allow them and the TSM administrator has to enable them.
• Content owners can only subscribe other people if the optional "let content owners subscribe other users" site setting is turned on. Otherwise only administrators and project leaders with the right site role can.
• Sites can set an optional From address and email footer, which also apply to data-driven alerts, while including quality warnings and sensitivity labels requires Tableau Catalog.

There is also a failure policy worth knowing before you rely on a report: by default a subscription is suspended after five consecutive failures. Server administrators can change that threshold. Owners and administrators can resume a suspended subscription from its menu — but the suspension itself is quiet, so a report can stop without anyone realising until a stakeholder asks where it went.

Data-Driven Alerts: The Other Email Path

Subscriptions are time-based. Data-driven alerts are condition-based: they fire when a number reaches a threshold you set, and they can be delivered by email, inside your Tableau site, or in Slack through the Tableau for Slack app.

The constraints are narrower than most people expect, and they are about chart geometry rather than data:

• You create an alert by selecting a continuous numeric axis on a chart. That is the anchor, and numeric bins and discrete numeric axes are not supported.
• Gantt charts and maps are excluded, and alerts work on dashboards and views but not on story points.
• For time-based charts, Tableau recommends relative date filters so recipients get alerted as new data arrives rather than against a frozen window.

Anyone with access to a view can see alerts other people created and add themselves with Add Me. Alert owners can change the threshold, schedule and recipients.

Alerts fail for ordinary operational reasons — a temporary connectivity problem, a data source that was removed, expired credentials, a workbook or sheet that was deleted. After enough failures the alert is suspended and the owner is emailed. Only the owner can edit a failing alert directly, which becomes a problem when the owner has left the company.

Want to know which keywords you're missing? Get your free SEO audit and find the gaps in minutes.

When to Use Which

The choice is usually obvious once you ask what the recipient is supposed to do with the email.

Use a subscription when:

• Someone needs the same numbers at a predictable time, and the report is a ritual: a Monday pipeline review, a month-end summary.
• The value is in seeing the shape of the whole dashboard.
• The recipient will open the live view if something looks odd.

Use a data-driven alert when:

• Nothing needs to happen unless a number moves.
• The threshold is the whole point: stock below a level, error rate above one, a target missed.
• You would rather send nothing most weeks than send a report nobody reads.

Use neither when:

• The recipient needs the underlying rows, or needs to filter and drill. Email delivers a picture, not a dataset — send them a link and the right permissions instead.
• You need delivery to people who are not Tableau users at all.

That last case is the common one, and it is worth being blunt about: subscriptions go to Tableau users. If your audience is a client, a board member or a colleague without a licence, built-in subscriptions are not the answer.

Limitations Worth Planning Around

Beyond the traps already covered, a few things reliably surprise teams:

• Delivery timing is best-effort. Tableau states that delivery may be delayed if server load is high. A subscription scheduled for 8:00 is not a guarantee of 8:00.
• "When Data Refreshes" has preconditions. It is available when the workbook uses one data extract on a published connection, and it sends only after refresh schedules have run. It is not supported for content that uses Tableau Bridge to stay fresh.
• PDF and PNG are not interchangeable. Pulse metrics render in PNG snapshots but not in PDFs, so if your dashboard includes them, test the format you chose.
• You cannot edit a subscription message after the fact, and nothing here is a data export. Changing the message means unsubscribing and re-adding every recipient, and there is no built-in "email me the CSV" option on a schedule.

None of these are reasons to avoid subscriptions. They are reasons to test with Run Now, scope to a custom view, and avoid promising precision the feature does not offer.

Tableau vs the Alternatives

Every major BI tool solves this, and the differences are mostly about who the recipient is.

• Power BI offers subscriptions and alerts on a similar model, with the same basic constraint that content must be published to the service rather than sitting in Desktop.
• Looker Studio sends scheduled PDF emails and will deliver to arbitrary email addresses, which makes it easier when your audience is outside your licence pool.
• Third-party distribution tools exist specifically because Tableau subscriptions stop at Tableau users and do not export data. If you need per-recipient filtering, bursting to a hundred clients, or Excel attachments, that is the category to look at.
• A scheduled script against the REST API is the honest answer for anything genuinely custom. Tableau exposes subscription methods in its REST API, and teams that need conditional routing usually end up there.

The pattern is consistent: Tableau's built-in email is excellent for internal, licensed, snapshot-shaped reporting and poor for everything else. Knowing which side of that line you are on before you build saves a rebuild later.

Final Thoughts

So — can Tableau send email reports? Yes, two ways, and both work well inside their boundaries.

Subscriptions handle the scheduled ritual. Data-driven alerts handle the exception. Both need the workbook published to Tableau Cloud or Tableau Server, both need an administrator to have enabled email on the site, and both deliver an image or a PDF rather than something anyone can interact with.

The failures are rarely technical. They are the group that silently never expanded, the filter that was never saved as a custom view, the subscription that suspended after five quiet failures, and the stakeholder who wanted the data and got a screenshot. Set it up, run it once with Run Now, and check that what arrived is what somebody actually asked for.

If you are still deciding where your Tableau content should live in the first place, our guide to what Tableau Cloud is covers the hosting side of that decision in detail.

Ready to stop guessing which pages are worth your time? Get a free SEO audit and see exactly where your site stands in search.