TABLEAU QUESTIONS

Do New Group Members Automatically Receive Tableau Subscriptions?

The new manager misses Monday’s sales report, while the colleague who changed roles still receives it. The group roster is right, but the report’s audience has not followed it.

Advanced Tableau Report Scheduler (ATRS) can use maintained reporting assignments at run time, keeping each person’s region and delivery details together as the team changes.

THE PROBLEM AND ANSWER Make sure the next sales report reaches the current team
YOUR OPTIONS Choose how the reporting audience stays up to date
SET IT UP Keep each recipient with the report they should receive
FOR DEVELOPERS Maintain the audience from your application
YOUR NEXT STEP Give joining and leaving the same attention

THE PROBLEM AND ANSWER Make sure the next sales report reaches the current team

A new regional manager joins the sales group on Friday but misses Monday’s report. The colleague who moved to another role still receives it. The group roster looks right, so the reporting owner naturally expects the email audience to match.

Tableau’s group subscription does not continuously follow that roster. It creates subscriptions for the people in the group at the time. Adding someone later does not add them to that existing delivery, and removing someone does not automatically remove their subscription while they retain the required view access.

A changed group roster needs a corresponding change to this report’s audience.

Check the new manager’s membership in Tableau first, then review the weekly report’s subscribers. Re-subscribe the group to include the newcomer and have the reporting owner or administrator address the former manager’s subscription and access.

For a small, steady audience, that review can be a manageable part of joining and leaving the team. Give one person responsibility for it, so the next role change does not depend on someone remembering why Monday’s email behaved differently.

When the audience changes regularly, ATRS offers another approach. A maintained query can return the current reporting assignments at run time, pairing each recipient with the region, format and destination they need.

Keep native subscriptions when PNG or PDF snapshots meet the requirement and the reporting owner can maintain the audience reliably. A group makes the initial selection convenient, but subsequent changes still need that owner’s attention.

If everyone receives the same file, an ATRS email destination can use a database query or a maintained text-file list. It also supports address-book recipients and groups. Choose the source that your team already keeps accurate, then test how changes reach the next delivery.

If each manager needs a different region or file, use an ATRS data-driven schedule. Its driver records can supply report parameters, output formats and delivery instructions at execution time. A newly approved assignment can enter the next selection; an inactive one can be excluded.

That is more useful than keeping a second list of email addresses beside a separate list of regional filters. The reporting owner can maintain who receives what together, while the schedule handles the recurring export and delivery.

Native membership behavior and choosing an ATRS recipient source

Tableau’s subscription instructions explain group additions and removals. To subscribe other users, you need workbook ownership, administrative authority or project leadership with an appropriate site role. Recipients need View and Download Image/PDF permissions. Confirm the newcomer appears in Tableau if a directory process maintains membership.

An ATRS Email destination can select To, CC and BCC addresses from supported address books, a database source or a text file. Its documented text-list format is one address per line without delimiters. An Excel-maintained roster can feed a suitable query or prepared text list through your maintained process; do not assume a worksheet automatically synchronizes with Tableau groups.

Use a Data-Driven Schedule when each returned row also controls report inputs and delivery choices. This does not automatically synchronize a directory or Tableau group. Define how approved changes reach the reporting records and who owns their accuracy. ATRS supports Tableau Cloud only.

For the native route, open the published view and choose Watch > Subscriptions. Re-subscribe the group after confirming its current membership and required content access. Keep the intended view, snapshot format and Monday schedule.

Use the published view’s Watch menu to reach subscription controls, then review the intended report audience.

Review the departing manager’s specific subscription as well. Removing a group membership alone may leave that delivery in place. Make the change for this reporting assignment while preserving other access and subscriptions the person still needs.

For the ATRS route, agree which records represent current reporting assignments. The new manager should appear with the correct region and destination; the former assignment should be excluded. Inspect those returned rows before running the report.

Create the data-driven schedule for the Tableau Cloud sales report and map the selected fields to its report inputs and destinations. Start with a known reporting week and controlled test addresses. Open the resulting files and compare the region, period and sales totals for each sample assignment.

The file can fit the reader too. One manager may want a PDF; finance may need Excel Data Only in its weekly template, with useful tab names, totals, number formats and a workbook password. Related reports can be sent together or merged into a PDF or Excel review pack.

Check the additions, exclusions and delivered contents, then enable the recurring run. Assign ownership of the audience source so the next personnel change reaches the reporting job as part of the normal process.

Driver setup, output options and pending deliveries

The driver needs a unique key for each returned row. Use the documented database connection setup and check that the ATRS service account can read the source when nobody is logged in. Map the recipient and report values deliberately, and inspect the sample results before delivery. Grouping reports by email address disables embedding them in the message body.

The Excel guide covers Excel and Excel Data Only XLSX output, worksheet naming, passwords and file properties. Data Only adds template placement, selected row or column totals, reusable styles and typed column formats. Test the prepared workbook, including any existing formulas or template areas.

For multiple reports, the Data-Driven Package guide covers grouping and PDF or Excel merging. Check the combined content and the recipient pairing before enabling the full audience.

Changes to the driver affect future selections. Review already queued, generated or deferred work separately; changing a record does not recall a message already delivered. Also check other schedules and recipient sources if the same person receives this report through more than one route.

If your application owns reporting assignments, keep its approved additions and departures connected to the audience source. A data-driven job can read those maintained records; an application maintaining a fixed ATRS email destination can use the destination API instead.

The application should check the saved audience after a change and retain enough information to trace the next delivery. These are ATRS reporting changes, separate from native Tableau group subscriptions.

API options for maintaining and checking recipients

For a fixed destination, SingleSchedule/UpdateEmailDestination selectively updates it by DestinationId. A nonempty To array replaces the To recipients; an empty or null To preserves them. For Cc and Bcc, null preserves the current list and an empty array clears it. Omitting those fields can clear them, so set them deliberately. See Update an email destination.

To add a separate destination, SingleSchedule/AddEmailDestination uses the report’s ParentId. Retain the returned DestinationId. Keep clearExisting=false when other email destinations must remain; true removes existing email destinations before insertion. See destination management.

For a complete SingleSchedule/Update, retain the full intended schedule definition and every destination that should survive, including its identifier. Omitted destinations can be deleted. Avoid using a full update merely to make a small recipient change when the selective operation meets the need.

After checking a fixed ordinary single-report job’s saved recipients and test destination, the following separate request runs it. Replace 101 with its actual UniqueId. Use your ATRS HTTPS address and keep the token on the backend. For a data-driven job, follow the documented execution contract for its stored schedule.

POST /api/Schedule/ExecuteScheduleAsync
Authorization: Bearer <ATRS-access-token>
Content-Type: application/json

{
  "ScheduleType": "report",
  "UniqueId": 101,
  "RunBy": "Reporting application"
}

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

Save the returned ExecutionId and parse the JSON-encoded ResultJson when monitoring the run. Completed can contain Result=false. Verify the resulting audience and file. After an uncertain response, reconcile saved destinations and executions before repeating a change or send. The execution guide explains tracking.

Do New Group Members Automatically Receive Tableau Subscriptions?

Make sure the next sales report reaches the current team

Include reporting in the handover

Choose how the reporting audience stays up to date

Use the roster someone already maintains

Keep each recipient with the report they should receive

Let the new manager see a first copy

Maintain the audience from your application

Leave a useful change record

Give joining and leaving the same attention

Contributors:

Christian Ofori-Boateng

About ChristianSteven Software