Tableau Report Delivery

Automate Tableau Report Delivery to Email and File Destinations

Put your finished Tableau report where its recipient can use it. ATRS delivers the file to your configured destinations and records the result for each one. You choose the access settings and recovery response for the routes you use.

Send finished files to email, folders, transfer servers or storage.

Set the account and path for each destination.

See which deliveries succeeded and which need attention.

Plan retries, failure notifications and retained-file recovery for the chosen routes.

The Reporting Challenge

Why Tableau Report Delivery Needs More Than an Export

A finished file still needs a reachable destination, the right access and a clear delivery result. Configure those handoff details before making delivery recurring.

Choose a Route the Recipient Can Access

A manager may collect a PDF by email while an operations process reads a file from a network folder. Match the destination to the receiving process.

Configure Destination Access

Use the account, credentials and path required for the selected destination. The receiving person or system also needs access to the final file.

Review Each Handoff

A file can be produced successfully and still fail at a destination. Plan the retry, notification and recovery response for the route in use.

Choosing the Right Approach

Native Tableau Delivery or ATRS Destinations?

Use Tableau subscriptions when an image or PDF email to permitted Tableau users meets the need. Use ATRS Tableau report delivery for configured file destinations, per-destination results and a recovery plan for failed handoffs.

Requirement	Tableau native and owned exports	ATRS
Delivery route	Standard view/workbook subscriptions email PNG/PDF snapshots. Authorized exports and owned integrations can provide other handoffs.	Configure the supported email, folder, transfer or storage destination required by the receiving process.
Destination configuration	Subscriptions require permitted Tableau recipients. An owned export or transfer integration needs its own account and target-path configuration.	Select the destination account and receiving path in the report schedule.
Results and recovery	Tableau can suspend failing subscriptions and allows resuming them. Owned file transfers maintain their own recovery behavior.	Inspect each destination result and configure supported retry, notification or recovery tasks.

Native guidance: Tableau subscriptions

See ATRS Tableau report scheduler for the product overview.

Choose the Route Your Reporting Job Needs

Deliver a usable file to the place your audience works. Choose the destination and final filename expected by the receiving team or business system.

Email

Deliver the finished attachment to approved addresses through the configured mail account. Check the sending server’s applicable limits.

Email Destination Guide →

FTP and SFTP

Configure the destination path, credentials and protocol-specific connection settings. Verify the connection and inspect the transfer result. Choose the retry settings available for the configured transfer.

FTP Destination Guide →

Cloud Storage: S3 and Azure

Use the configured storage account and required bucket, container or folder path. Confirm that the receiving process can access the saved file.

Amazon S3 Destination Guide → Azure Blob Storage Guide →

Folders, Teams and SharePoint

Route finished files to the approved folder, channel or document location. Configure the access and supported metadata required for that destination.

Browse Destination Guides →

Recover the Destination That Needs Attention

If one destination fails while another succeeds, History View marks the run as Partial Success. Expand the run to identify the failed destination.

Keep a Recoverable File

Enable snapshots in the schedule’s Settings and choose how long to keep them. Confirm the snapshots folder in System Paths and check whether folder housekeeping could delete files before your recovery window ends.

Correct the Failed Route

Fix the failed destination’s credentials, connection or path. Review the already-successful routes before deciding what to resend.

Choose the Recovery Action

Choose whether to retry the configured job or deliver a retained file. For FTP recovery, configure an Upload File(s) custom task with the retained file and target directory, and verify how the task will be invoked. If the required file was not retained, regenerate it with the original reporting values.

History View guide · Snapshot settings · System Paths · FTP custom tasks.

START FREE TRIAL BOOK A DEMO

A magnifying glass highlights one report-delivery destination, with a retry symbol beside it.

Worked example

One File, Two Routes, One Failed Handoff

For example, on 13 October 2026, a supplier-planning process needs the completed order file for 12 October in an internal network folder and a supplier FTP directory.

Part of the handoff	Example requirement
Finished file	supplier_orders_2026-10-12.csv, covering 12 October activity.
Network-folder route	Disk destination → \\reports.example.com\supplier-planning\supplier_orders_2026-10-12.csv.
FTP route	Configured FTP destination → /incoming/orders/supplier_orders_2026-10-12.csv.
Reported result	The network-folder delivery succeeds; FTP reports an authentication failure. Inspect both destination results under Partial Success in History View.
Recovery	The reporting operator corrects and verifies the FTP credentials, locates the retained 12 October file and delivers it to the supplier directory using the configured transfer procedure. Check the retry or resend scope before acting so the successful network-folder delivery is handled deliberately.
Acceptance	The supplier-planning process confirms that it can retrieve the file and process the 12 October orders. A transfer result alone does not establish ingestion.

Define the Handoff Before the First Recurring Run

Start with the final path, filename and person or process that will collect the file. Give the ATRS service identity the source and destination access required by that route.

Agree the Receiving Location

Record the mailbox, folder or storage path and the destination-specific access settings.

Agree the Failure Response

Decide who receives failure notifications, who handles recovery, which retry options apply, how long the output must be retained and how repeat deliveries should be handled.

ATRS uses a supported Windows host connected to Tableau Server or Tableau Cloud. Review installation prerequisites. For the wider product, see ATRS Tableau report automation.

For the file itself, see PDF output and protection, Excel output and templates or CSV specifications.

Trusted Report Automation for More Than 20 Years

ChristianSteven Software has helped organizations automate business intelligence reporting and delivery for more than two decades.

20+

Years of reporting automation experience

Nearly 5,000

Organizations helped worldwide

Countries with customer organizations

SOC 2 Type II

Independent assurance over security and operational controls

Visit Our Trust Center →

Technical Support

Get help with ATRS setup and configuration

Current Capabilities

Follow ATRS release announcements and product guides

Enhancements

Discuss your reporting requirements with the ATRS team

ATRS Email Log records SMTP messages. For Exchange or Office 365, check the sending account’s Sent Items folder. Use schedule History View to review report and destination results.

Delivery options include email, local and network folders, FTP/SFTP, Microsoft Teams, SharePoint, Amazon S3 and Azure storage. Choose the destination and account required by the reporting job.

Recipients can read delivered files without opening Tableau. The exporting account needs the appropriate Tableau permissions and licensing; receiving a static file does not grant access to the source workbook.

Install ATRS on a supported Windows host and configure its unattended service with the source and destination credentials needed by the reporting job. The host must remain running; the Windows Service allows scheduling to continue while nobody is logged in.

Review the result for each configured destination and check the actual final path and filename. Confirm separately that the receiving person or system can retrieve and use the file. Upload success alone does not prove reading or ingestion.

Yes, where the configured destination or job provides retry options. Choose the failure response and verify its scope. Review History View so you know which destinations already succeeded before retrying.

If snapshots were enabled and the file is still retained, locate it in the configured snapshots folder and confirm its reporting period. Deliver that saved file using the configured recovery procedure for the failed destination. If it is unavailable, regenerate it with the original reporting values.