Tableau subscriptions deliver dashboard and view snapshots via email or Slack on a schedule. Here is how to configure them, what the common failure modes are, and how to govern them at enterprise scale.
The quick answer
Tableau subscriptions deliver snapshots of views or dashboards via email or Slack on a schedule. Users receive a PNG image or PDF of the view as it appears at the scheduled time — with any relevant data filters applied — without needing to visit Tableau Server or Tableau Cloud. For organisations with executives or stakeholders who want regular data updates without actively using the BI platform, subscriptions are the primary delivery mechanism. The common failure modes — subscriptions that never deliver, subscriptions that deliver blank images, and subscription lists that grow uncontrolled — are fixable with proper configuration and governance.
How subscriptions work
When a subscription fires, the Tableau Server backgrounder process renders the subscribed view at the scheduled time, captures the output as an image or PDF, and emails it to the subscriber list. The rendering happens with the subscriber's permissions and data access — if the subscriber does not have access to certain data due to row-level security, the subscription image reflects that restricted view.
**What gets delivered**: a PNG image of the current view state by default. For dashboards with multiple tabs or paginated reports, PDF delivery captures all tabs. The image represents the view as it would appear to the subscriber on the website at that moment.
**Schedule options**: hourly, daily, weekly, and custom cron schedules (on Tableau Server; Tableau Cloud has fixed schedule options rather than arbitrary cron). Delivery time should be set for when the underlying data is fresh — a 6 AM subscription delivering yesterday's data that finished loading at 5:45 AM is clean; a 6 AM subscription where the data loads at 6:30 AM delivers stale data.
**Subscriber management**: site administrators can view all subscriptions on a site, see who is subscribed to what, and manage or delete subscriptions. Users with the appropriate permissions can subscribe themselves and others (if granted that permission by the site administrator).
Setting up subscriptions
**For individual users**: navigate to any view in Tableau Server or Cloud, open the menu, and select "Subscribe". Choose the delivery schedule, the format (image or PDF), and optionally add a custom message. The subscription is tied to your account — if your account is deactivated, the subscription stops.
**For groups**: administrators can subscribe a group to a view, delivering to all group members simultaneously. Group subscriptions are efficient for standing distribution lists (a weekly executive dashboard delivered to the Executive Leadership group).
**Via REST API**: subscriptions can be created, listed, updated, and deleted via the Tableau REST API. This enables programmatic subscription management — creating subscriptions for all members of a group, updating subscription schedules in bulk, or auditing all subscriptions across the site.
Common failure modes
**Subscriptions delivered but image is blank or shows an error message**: most commonly caused by:
- The underlying extract failed to refresh before the subscription fired. The view loaded but showed "No data available" because the extract was stale or empty. Fix: ensure extract refresh schedules complete before subscriptions fire; set up monitoring for failed extract refreshes.
- Row-level security filtered all data for the subscriber's account. The view is technically valid but shows no data for that user. Fix: verify the subscriber's account has appropriate data access before adding them to subscriptions.
- The view contains a live connection to a database that was unavailable at subscription render time. Fix: switch to extracts for views distributed via subscription.
- A Tableau Server backgrounder process failure during rendering. Fix: check backgrounder logs in Tableau Server admin for errors at the subscription time.
**Subscriptions not delivering**: check:
- SMTP configuration on Tableau Server (Admin > General > Email Server). An incorrect SMTP hostname, port, or credentials causes all subscription delivery to fail silently from the user's perspective.
- Recipient email addresses in your organisation's spam filter or email security appliance. Tableau Server email often requires whitelisting.
- Backgrounder process availability. If all backgrounder processes are consumed by extract refreshes when the subscription fires, the subscription is queued and delayed. Monitor backgrounder utilisation.
- Suspended subscriptions. Tableau Server automatically suspends subscriptions that fail repeatedly. Check Admin > Subscriptions for suspended status and re-enable.
**Subscriptions delivering at the wrong time**: verify the Tableau Server timezone configuration matches the expected delivery timezone. Tableau Server's subscription schedule is in the server's configured timezone, not the subscriber's timezone. An 8 AM subscription on a server configured to UTC delivers at 8 AM UTC — which is 3 AM Eastern Time.
Subscription governance
At enterprise scale, subscriptions without governance create problems: stale subscription lists that continue delivering to departed employees, subscription sprawl that creates unexpected backgrounder load, and subscriptions based on views that have been deprecated or moved.
**Audit subscriptions regularly**: use the Tableau REST API to list all subscriptions on the site (GET /api/version/sites/site-id/subscriptions). Identify subscriptions for users who are no longer active, subscriptions for views that are stale or deprecated, and subscriptions with very high subscriber counts that may be abusing the subscription mechanism.
**Decommission with deactivation**: when a user's Tableau account is deactivated (typically when they leave the organisation), their subscriptions do not automatically deactivate — they may transfer to another account or continue delivering. Include subscription deactivation in the user offboarding process.
**Subscription load planning**: each subscription generates a backgrounder job that renders the view. A 7 AM batch of 200 subscriptions for a complex dashboard with live connections can saturate backgrounder processes and delay other scheduled jobs. Schedule high-volume subscription deliveries in off-peak windows, or stagger them.
**Preferred alternative for high-volume distribution**: for very large subscriber lists (hundreds or thousands of users), consider embedded analytics or a data portal approach — a lightweight web page that renders live Tableau views — rather than email image delivery. Images do not support interaction, lose resolution on retina displays, and are not accessible for users with visual impairments.
Slack integration
Tableau Cloud and recent Tableau Server versions support Slack delivery for subscriptions — the view is delivered as an image to a Slack channel or direct message instead of (or in addition to) email. This is increasingly the preferred delivery mechanism for data-first organisations that live in Slack.
Configure Slack integration in Tableau Cloud (Manage > Connected Apps > Slack) or Tableau Server admin settings. Once connected, users can select Slack delivery when creating subscriptions.
For the broader Tableau Server administration context, see tableau server admin guide. For extract refresh management that affects subscription reliability, see tableau data sources guide. For Tableau Cloud migration where subscription behaviour differs, see tableau server to cloud migration.
Our managed BI services and Tableau consulting practices manage Tableau Server and Cloud environments — including subscription governance, backgrounder capacity management, and user lifecycle automation. Book a free 30-minute audit to discuss your Tableau environment.
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 →