How Do You Audit Who Changed or Ran an Automated Tableau Report Schedule?

Imagine the reporting owner investigating a customer’s unexpected monthly attachment. The file arrived, but someone changed the schedule earlier in the week. Finance wants to know which user made the change and which reporting run produced this copy.

Those are related questions with different evidence. ATRS’s Audit Trail records activities such as users editing, refreshing or executing schedules. History View helps investigate a particular reporting run and its destinations.

Keeping both available makes the conversation easier to continue. The owner can follow the configuration activity, then inspect the execution and file, instead of trying to reconstruct everything from inbox messages.

Conceptual illustration: Report files routed to the people and locations that use them.

For an occasional delivery question, the saved schedule and History View may be enough. You can inspect what ran and which destination needs attention.

When several people maintain customer reporting, an activity record serves another purpose: it helps identify who performed the recorded schedule actions. ATRS stores its Audit Trail in an external ODBC-compliant database you configure for that purpose.

Agree access and retention with the person responsible for that database. An activity entry is useful evidence, but it should not be presented as a complete, immutable compliance record or proof that someone received and read a report.

Begin with a test schedule and the question finance wants to answer. Ask the database owner to provide the approved external Audit Trail database and connection access.

In ATRS Options, open Audit Trail, enable it and configure that database connection. Confirm the connection before applying the setting. The reporting team now has a place for the activity record it expects to use.

Make a controlled change with a known authorized user, then run the test report. Review the recorded action with the schedule owner and compare it with the reporting history and actual test delivery.

Have another colleague use the records to explain the test without relying on your memory. Once the evidence supports that handover, agree how the database is retained and who reviews activity when a reporting change is questioned.

The Audit Trail settings configure the external database used for the activity record.

An application can keep the customer’s authorized request with its ATRS execution reference. That connects the action people recognize with the particular reporting run.

Use the application’s own authenticated user record for identity, and retain the outcome needed for the reporting review.

GET /api/Schedule/GetExecutionStatus?ExecutionId=<retained-execution-id>
Authorization: Bearer <ATRS-access-token>

The reporting owner can answer finance with an activity record, a particular run and the document it produced. The next question has a traceable starting point rather than another search through emails.

Use one controlled schedule change to evaluate the records your team needs. It gives the ATRS audit configuration a concrete business purpose.

Explore ATRS reporting oversight and delivery