Tableau Subscriptions With Filters: How to Set Them Up

You can send a filtered Tableau subscription, but only through a workaround. Set your filters on the dashboard, save the result as a custom view, then subscribe to that view instead of the original. That covers one audience with one set of filters. If every recipient needs different filters, or some recipients are outside your organization, native subscriptions get awkward fast. This guide covers both cases.

TL;DR

• Native Tableau subscriptions follow the view you pick. To get filters into the email, save a custom view and subscribe to that.
• One custom view serves one filter combination. Fifty regional managers means fifty custom views to build and maintain.
• Recipients generally need the right content permissions in Tableau, which matters when you want to reach external people.
• When you need per-recipient filtering, Excel or CSV attachments, branded email or external delivery, a dedicated automation tool such as our ATRS is the cleaner route.
• Check the filter logic in your first test email before you roll anything out to a distribution list.

Table of Contents

• How native Tableau subscriptions handle filters
• Step by step: subscribe to a filtered custom view
• Subscribing a distribution list
• Where native subscriptions run out
• Reaching external users without Tableau licenses
• What a recipient-specific filtered report looks like
• Conditional subscriptions: send only when it matters
• Our perspective: filters are a distribution problem, not a dashboard problem
• A checklist before you roll out filtered subscriptions
• Automating filtered Tableau delivery with ATRS
• FAQ
• Sources

How native Tableau subscriptions handle filters

A Tableau subscription sends scheduled email updates of a workbook or a specific view. According to a University of Michigan knowledge base article, the email carries the most recent version of the report as a PDF or an image, plus a link back to the dashboard, at the intervals you choose.

The important detail is that a subscription points at a view. It does not carry the filter choices you happened to click a minute ago. Subscribe to the default view and everyone gets the default filters, however carefully you set up the dashboard in your browser.

There are three practical ways to get filtered content into a subscription:

1. Custom views. Save your filter selections as a named view, then subscribe to it.
2. Filters baked into the dashboard. Build a dedicated worksheet or dashboard with the filter fixed, and subscribe to that.
3. Conditional logic in the data. Build a calculated field that flags the condition you care about, filter to it, and let the subscription send something only when relevant rows exist. TAR Solutions describes this pattern for flagging bad records, and it is the closest native answer to conditional subscriptions.

Step by step: subscribe to a filtered custom view

The exact menu labels shift between Tableau Server and Tableau Cloud versions, so treat these steps as the general flow.

1. Open the published dashboard in your browser.
2. Set the filters, parameters and selections you want the recipients to see.
3. Click View at the top of the dashboard and save the current state as a custom view. A University of Kentucky quick start guide walks through this sequence: set the filters, click View, pick the right view.
4. Give the view a name that says what it contains, such as "Northeast Region, Open Orders". You will thank yourself when you have thirty of them.
5. With that custom view selected, click Subscribe.
6. Choose the recipients, the schedule and the format (image or PDF).
7. Send yourself a test first and compare the numbers to the live dashboard.

InterWorks has a useful walkthrough of custom subscriptions with custom views. It also shows the older workaround many teams used before this was built in: a PowerShell and tabcmd script on a Windows scheduled task. That still works, but someone has to own the script.

Custom views, public or private

A custom view can be private to you or made public so others can select it. That choice matters. If you subscribe colleagues to your private view, they may not be able to see or manage the same filtered state themselves. Decide up front who owns each custom view, because a view that disappears when its owner leaves will quietly break the subscription built on it.

Sharing a filtered view without a subscription

Sometimes you do not need a schedule. Salesforce's Trailhead module on sharing views explains that when you change marks or filters and click Share, Tableau generates a new unique link. To share a saved custom view, open it and use any sharing option. That is a good fit for one-off requests, but it is a link to a live view, not a delivered report.

Subscribing a distribution list

A frequent follow-up: can you subscribe a whole distribution list? Natively, you add users one at a time or select several by name. The University of Michigan guide notes you can search for users and select multiple, or subscribe on behalf of others. Those users must exist in Tableau. An email distribution list that lives only in your mail system is not something a native subscription can target.

That has three consequences:

• Every recipient needs a Tableau account, so list membership changes become Tableau administration.
• New hires do not receive anything until someone adds them.
• Everyone on the subscription gets the same filtered view.

For a team of ten, that is fine. For a few hundred recipients with different needs, the maintenance adds up.

Where native subscriptions run out

Native subscriptions are good at what they were designed for: a licensed user wants a regular snapshot of a dashboard. A Confluence guide from Pittit Analytics describes the same model: image or PDF snapshots, links back to the dashboard, and schedules that are either regular or tied to data refreshes.

The limits show up in specific situations:

This is not a criticism of Tableau. The split is a design choice, and it is a sensible one. Our job is to cover the cases that fall outside it.

Reaching external users without Tableau licenses

This is the question we hear most from IT managers. A customer, auditor, franchisee or board member needs a monthly report, but you do not want to create a Tableau account for them.

The Tableau Subscription guide on our blog makes a point worth repeating: subscriptions do not replace licenses. Tableau's own documentation, as summarized in the sources above, describes subscription recipients as users with the required content permissions. Someone outside your Tableau site generally cannot be a native recipient.

You have three realistic options:

1. Give them an account. Simple, but it costs a license and puts an outsider inside your analytics environment.
2. Send them a link. They still need access to the view, so this runs into the same permission question.
3. Deliver a file. Export the filtered report as a PDF or Excel file and email it, or drop it in a shared location. The recipient needs nothing but an inbox. This is the approach automation software exists to handle.

The third option also fits the filtering problem. If the file is generated per recipient, each external party sees only their own data, and nobody has to be trusted with a live dashboard that holds everyone's numbers. You still need to confirm that your filtering logic really isolates each recipient's rows, and your security or compliance team should sign off on the process before external delivery starts.

The same logic applies to the neighboring questions readers ask about Power BI and SSRS. Power BI sharing generally depends on the recipient's licensing and access, and SSRS subscriptions depend on how the report server is set up. In each platform, file-based delivery is how you reach people who sit outside the system. We cover Power BI and SSRS with PBRS, and the same recipient-specific approach applies.

What a recipient-specific filtered report looks like

Here is a worked example. A distribution company has 80 sales reps and a Tableau dashboard of open orders with a Rep filter.

The native way: create 80 custom views, one for each rep, then create 80 subscriptions. When a rep leaves, someone deletes a view and a subscription. When a territory changes, someone rebuilds a view. When you add a column to the dashboard, check that all 80 still behave.

The data-driven way: keep one dashboard and one list of recipients, each paired with their filter value, usually in a database table or spreadsheet. A scheduler reads the list at run time, applies each rep's filter, exports the result and emails it. A new rep means a new row. A departed rep means removing a row.

The second approach is what we mean by data-driven bursting, and it is the main reason teams come to us. Our Tableau scheduler page describes generating recipient-specific reports using data-driven filters and parameters.

Conditional subscriptions: send only when it matters

Many users do not actually want a daily email. They want an email when something is wrong: inventory below a threshold, a missed target, an unusual number of failed records.

With native tools, the usual pattern is the one from the TAR Solutions article linked above. You build a calculated field that is true for the problem rows, filter the view to that condition, and subscribe. The TAR Solutions example uses it to catch bad email address records. Check how your Tableau version handles a subscription whose view returns no data, because behavior varies and an empty snapshot arriving every morning teaches people to ignore your emails.

The more flexible version is event-triggered delivery, where an external condition (a data load finishing, a row appearing in a table, a file landing in a folder) decides whether the report goes out. That keeps reports tied to the moment the data is ready instead of a guessed clock time. Our guide on how to schedule refresh in Tableau covers the refresh side, which matters because a subscription sent before the extract refreshes shows yesterday's numbers.

Our perspective: filters are a distribution problem, not a dashboard problem

Most teams treat a filtered subscription as a dashboard feature. They keep adding custom views and tweaking filters until the dashboard feels right. In our experience, the real issue is distribution.

A dashboard answers "what does the data say?" A subscription answers "who needs to know, in what format, and when?" Those are separate questions with separate owners. Analysts own the first. IT and report administrators own the second, and they feel the pain when reporting demands outgrow native scheduling.

So we suggest a simple test. If one filter set serves one audience, native subscriptions with custom views are the right tool, and you should use them. Once you are managing recipients by hand, copying subscriptions, or answering help desk tickets from people who did not get their report, the problem has moved from building reports to delivering them. That is where we built ATRS, PBRS and CRD to help: formatted, personalized, securely delivered reports from Tableau, Power BI, SSRS and Crystal Reports, without a pile of scripts that only one person understands.

We also try to be honest about where native is enough. Our own Tableau scheduler page says that native subscriptions can email PNG or PDF snapshots to users with the required content permissions, on a schedule or after a supported refresh, and recommends ATRS when the job needs recurring Excel or CSV files, company-branded email, recipient-specific instructions, assembled report packs or file destinations. That is the line we would draw too.

— Christian Ofori-Boateng

A checklist before you roll out filtered subscriptions

Whether you stay native or automate, run through these before the first real send:

• Name your custom views clearly. Include the filter values and the audience.
• Decide who owns each view and subscription. Orphaned items cause silent failures.
• Confirm refresh timing. The report should run after the data refresh, not before.
• Test with a real recipient's access. What you see as an administrator may differ from what they see.
• Compare the first email to the live dashboard. A mismatched filter is easier to catch before 200 people receive it.
• Plan for failures. Someone should know when a send fails, rather than hearing about it from a director.
• Review external delivery with security. Confirm that each outside recipient can only ever receive their own data.

Automating filtered Tableau delivery with ATRS

ATRS is our Tableau report automation software. It generates filtered reports for each recipient, exports them as PDF, Excel or CSV, and delivers them by email or to file, cloud and collaboration destinations, on a schedule or when an event occurs. Recipients do not need a Tableau account. Our page on automating and sharing Tableau reports shows how it works, and you can see the full product line, including PBRS for Power BI and SSRS and CRD for Crystal Reports, on our product site. It is available as a subscription or perpetual license, following a free trial or demo.

For more depth, our guide to how to automate reports in Tableau is written for enterprise teams, and the Tableau subscription schedule article covers scheduling in more detail.

FAQ

Can a Tableau subscription include filters?

Yes, indirectly. Set your filters, save the state as a custom view, and subscribe to that custom view. The subscription then sends the filtered version rather than the default. Each different filter combination needs its own custom view.

Can I send each person a different filtered version of the same dashboard?

Natively, you do it by creating a custom view and a subscription for each person. That works for a handful of recipients and becomes tedious beyond that. Data-driven report automation reads a recipient list, applies each person's filter and sends individual reports in one scheduled run.

Can I email Tableau reports to people without Tableau licenses?

Native subscriptions are aimed at users with the required content permissions in Tableau. To reach people outside your organization, you can export the filtered report as a PDF or Excel file and email it. Automation software does this on a schedule so you are not exporting by hand.

Why does my subscription show unfiltered data?

Usually the subscription was created on the default view rather than a custom view. Open the saved custom view first, then click Subscribe from there. Also confirm the custom view still exists and is visible to the recipients.

Sources

• Tableau Dashboard Subscriptions, University of Michigan
• How to Set Up Email Subscriptions to Tableau Reports, Pittit Analytics
• Tableau Custom Views and Subscriptions 2-Pager, University of Kentucky
• Effective Sharing of Tableau Views with Others, Trailhead
• Tableau Conditional Alerts using Subscriptions, TAR Solutions
• Custom Subscriptions with Tableau Server Custom Views, InterWorks
• Tableau Report Scheduler Software & Automation, ChristianSteven
• Tableau Subscription: How To Automate Dashboards And Reports At Scale, ChristianSteven

Recommended

• Tableau Subscription: How To Automate Dashboards And Reports At Scale
• Tableau Subscription Schedule: How To Automate Enterprise Report Delivery
• Tableau PDF Subscriptions: Set Up, Troubleshoot, and Scale
• Tableau Subscription Schedule Options: A Practical Guide For Enterprise Reporting