Destinations#

Destinations on the Distribution step are the delivery targets for a report's generated files. Each target type is a distributor. A distributor is configured in two places: a global connection (Settings, Integrations, Distributors, holding credentials, defaults, and a Test Connection button) and a per-job destination added on the Distribution step (path, folder, or recipient fields, most of them tokenizable, see Name and organize output files).

A job can target multiple destinations at once, and each destination delivers only the output formats you route to it. The Destinations area shows no tiles until at least one distributor is configured in Integrations; ask your administrator if the tile you need is missing.

The destinations#

IBM Planning Analytics is a destination, not just a source. The PA distributor writes output files into an Application Folder. This is the opposite direction from the PA report provider, which reads source reports from application folders. Same "Application Folders", opposite direction, do not conflate them.

Box is browse and read-only as a source, and a full write destination. As a source report provider Box is used to load templates; as a distributor it writes output. (There is no separate limitation to note for Box delivery beyond the folder and versioning behavior above.)

Per-destination setup notes#

These are the non-obvious prerequisites that make a distributor work. Most are configured once, by an administrator, on the global connection.

Email (Microsoft 365 Graph): a non-default From needs a "Send as" grant#

With the Microsoft 365 Graph transport, sending "as" any address other than the authenticating account's own mailbox requires that account to hold Send as on the target mailbox. In the Exchange Admin Center, open Recipients, Mailboxes, the target mailbox, Delegation, Send as, and add the authenticating account. Without it, an override-From send fails.

Network Folder: the Bootstrapper service account needs write access#

The Network Folder connection has no credential field, only a Test Folder. The destination path is written by the Reportworq Bootstrapper service account, so that account (not the interactive user) must have write access to the target folder. Mapped drive letters are invisible to the service context; use a local path or a UNC path such as \\MyServer\MyFolder.

SharePoint: use the case-sensitive .../sites/<site>/... URL#

The Location must be the canonical, case-sensitive form https://<tenant>.sharepoint.com/sites/<site>/<folder1>/<folder2>, not the URL from the browser address bar (which is encoded or redirected and will not resolve). The authenticating account needs rights to create, delete, and update files in the target library.

Slack: four OAuth scopes plus the bot in each channel#

The Slack app needs four Bot Token OAuth scopes: chat:write and files:write (to post reports), plus channels:read and groups:read (to resolve a channel by name). Separately, the bot must be added to each target channel (in the channel, Integrations, Add an App), or posts fail. These are the two reasons a Slack distributor appears to "do nothing".

Teams: Direct (Graph) only, there is no Bot mode in v6#

Only Teams Direct (Graph) is wired. The Distribute path splits the target list into email addresses (sent as chats) and channel names (sent as channel messages), as the authenticated user. A "Teams Bot" mode is not shipped in v6, do not plan around a Bot send path.

SFTP: provision the server account first#

Reportworq needs a server-side, SFTP-enabled account with full permissions on a dedicated folder, so it can create the per-job subfolders it delivers into. The Host Address is the server's IP address.

How delivery behaves#

Use cases#

• Email a monthly P&L PDF to controllers with address-book recipients.
• Publish a board deck to SharePoint, delivered to a library folder built from a region token.
• Archive a timestamped Excel to a network folder per cost center.
• Notify a finance channel with a Slack or Teams post of the run's output.
• Hand off a CSV extract to a partner over SFTP.
• Round-trip a report into Planning Analytics, delivered back into a PA Application Folder so PA users open the same file in their model.

Notes and limits#

• Test Connection may not confirm per-job write access.
• OneDrive writes only to the delegated service account's own drive.
• Teams delivers only via the Direct (Graph) path in v6.

Going deeper. To send one combined email per recipient instead of many separate messages, and to zip or collate the outputs, see Combine emails, collate, and zip.