Why Is the Subscribe Option Missing in Tableau?

For the analyst’s first check, open the published dashboard directly in its Tableau Cloud or Tableau Server site, using the intended account. Look under Watch > Subscriptions. This separates the report itself from the portal that embeds it. A Tableau Desktop workbook is not the published subscription interface.

Work through these checks before changing the report’s delivery schedule.

If the control appears directly in Tableau but disappears in the portal, investigate the embedding and authentication configuration. Tableau documents that embedded views using restricted trusted authentication do not show Subscribe or Alert controls. That is a specific authentication condition; it does not mean every embedded dashboard lacks subscriptions.

If the control is absent in the direct published view too, check the user’s effective permissions and the data connection next. For native subscriptions, the recipient needs View and Download Image/PDF access. Ask the content owner or administrator to review those capabilities on the actual view rather than inferring them from a job title or a working dashboard link.

Also describe precisely what is missing. A visible subscription dialog without When Data Refreshes is a different problem from an absent Subscribe control. Bridge-backed sources, live connections and multiple extracts have particular refresh-trigger limitations. Changing email settings will not make an unsupported refresh trigger appear.

The Tableau subscription instructions show the published-view workflow. Use the Cloud troubleshooting guidance or Server troubleshooting guidance for your deployment.

The analyst can now give the administrator a reproducible report: the account, site, dashboard and whether Watch > Subscriptions appears outside the portal. That is more useful than requesting a general permission increase. Match the correction to the observed condition.

Tableau Server adds an administration layer: subscription email must be configured and allowed at the server and site levels. Its troubleshooting documentation also identifies missing or disabled subscription schedules as a cause of an absent icon. Do not look for customer-managed Server SMTP settings in a Tableau Cloud account.

If subscribing yourself works but adding colleagues does not, check who is permitted to subscribe other users. Ownership, administrative status and project leadership with the appropriate site role affect that action. Expanding the audience is a separate decision from restoring the analyst’s own subscription.

Restore the simplest suitable route first. If the analyst needs an ordinary Monday image or PDF, have the owner resolve the documented access or configuration issue, create the native subscription and inspect a received sample. There is no need to replace a subscription that meets the requirement.

Suppose the same sales update later needs an Excel file for finance and a PDF sent through the operations mailbox. A Tableau report scheduler becomes relevant because the deliverable has changed. ATRS can hold the report selection, export and destination configuration together for repeated delivery. It does not make unauthorized source content available.

In ATRS, open Integrations > Tableau > Add. Give the account a recognizable name and select the authentication type supported by your setup. Supply the server, site and required authentication details, select the API version and use Verify before Save & Close. Follow the ATRS Tableau account instructions for the fields required by that method.

A successful account verification is the starting point. Create a Single Schedule for the permitted sales report, select its output and reporting period, then preview that content. Configure a controlled test destination and use Tools > Test before extending delivery to the production audience. The ATRS Single Schedule guide explains the report workflow.

For the analyst, the benefit is a maintained export-and-send routine when the job grows beyond the original snapshot. Keep the source-access decision with the Tableau owner and the audience decision with the reporting owner.

A portal login, a Tableau source connection and an application request to ATRS serve different purposes. The analyst’s ability to open a dashboard in a browser does not prove that an unattended reporting process has usable credentials. Conversely, an absent portal Subscribe button does not establish that an authorized export integration is unavailable.

A live connection that requires someone to type database credentials cannot supply an unattended native subscription as-is. For OAuth-backed connections, review the supported saved or embedded credential arrangement and whether its refresh token remains valid. Tableau’s subscription access guidance explains the source-access requirements.

For an ATRS integration, keep the configured Tableau credentials separate from the credentials used to call the ATRS API. The former allow the reporting job to reach Tableau; the latter authorize an application to request an ATRS operation. Do not pass an analyst’s browser session to a background process or assume that a successful API sign-in grants access to every view.

If the portal eventually offers a report-delivery request, map the signed-in reader to an approved report configuration on the server. Keep source credentials and API tokens there. Test the requested report with that configuration and retain the request and execution result together. A hidden subscription control should not become a reason to expose an unrestricted export function.

Use the ATRS Developer Hub when building that application workflow. First establish the permitted source connection and a working report job; adding an execution request cannot repair missing source permissions.

Return to the original symptom and reproduce the analyst’s steps. If the native control was missing, confirm it now appears for the intended account in the intended view. Create the Monday subscription and inspect the received content. If only the embedded route remains different, document the supported route for the reader with the portal owner.

If the requirement has become a separate export-and-delivery process, test the ATRS job with the actual report, audience and output. Verify that the file contains the intended period and that its recurrence matches the reporting requirement. Choose the workflow based on that received result.

Explore ATRS for recurring Tableau report emails

Considering ATRS for your reporting workflow? Share the guide with the colleagues responsible for deployment, source access and delivery requirements.

Download the ATRS Internal Evaluation Guide