The Box distributor delivers the files a job generates straight into a folder in your organization’s Box account, creating any folders in the destination path on the fly and versioning files that already exist.

Box uses its own server-to-server connection (a Box Custom App using Client Credentials Grant), separate from the Microsoft 365 connection used by SharePoint and OneDrive. Once the Box app credentials are entered and the app is authorized for your enterprise, Box is ready to use.

Before you start#

A Box administrator needs to create a Custom App in the Box Developer Console:

• Choose Custom App with Server Authentication (Client Credentials Grant).
• Grant the app the Read all files and folders stored in Box and Write all files and folders stored in Box application scopes.
• Authorize the app for your enterprise (Box Admin Console → Apps → Custom Apps Manager).
• Note the app’s Client ID, Client Secret, and your Enterprise ID.

Configuration#

Open Administration → Distributors → Box.

• Enable distributor — turns the Box distributor on so it can be selected in a job.
• Client ID / Client Secret — the credentials from your Box Custom App. The secret is stored encrypted.
• Enterprise ID — your Box Enterprise ID (the service account the app runs as).
• Default Send As User (optional) — a Box user ID to send (impersonate) as for every job that uses this connection. A job step can override this. Leave blank to deliver as the service account.
• Base Folder (optional) — the main-level Box folder uploads are rooted at, entered as a folder path (for example Reports/2026). Each job’s folder path is created beneath it. Leave blank to use the Box account root.

Select Test Connection to verify Reportworq can reach Box, then select Save Changes.

Adding Box to a Job#

In a job’s distribution step, choose Box and configure the destination.

• Folder Path (optional) — the destination folder, resolved beneath the connection’s Base Folder. The field accepts variables/parameters (for example Reports/%Market Name%/2026), so the same job can route each report to its own folder. Any folders in the path are created automatically if they do not already exist. Leave blank to deliver directly into the Base Folder.
• Send As User (optional) — overrides the connection’s Default Send As User for this step. Leave blank to use the connection default.

The Options sidebar also lets you Zip Files (with an optional exclusion list) before delivery.

Behavior#

• Folders are created automatically. The Base Folder joined with the step’s Folder Path is created as needed; existing folders are reused and their contents are left untouched.
• Re-runs create a new version. Delivering a file whose name already exists in the destination folder uploads it as a new version in Box (not a duplicate), preserving Box’s version history.
• Large files use chunked upload. Files of 50 MB or larger are uploaded with Box’s chunked-upload API automatically.
• Impersonation precedence. Each file is delivered as the step’s Send As User if set, otherwise the connection’s Default Send As User, otherwise the service account.
• File names are flattened. Box file names are flat within a folder, so any directory portion of an output file name is dropped — folder structure comes from the Folder Path field.

Note: A distribution fails fast if neither a Base Folder (on the connection) nor a Folder Path (on the step) is set, to avoid delivering into the Box account root by accident.

See also: Box Documents (using Box files as report sources).