Skip to main content
When you run a report, Box saves the output file to a destination folder in your account. The default destination is Box Reports. You can choose a different folder so reports land where people already work, instead of moving files after each run. Who can choose a destination depends on which report you run:
  • Admin Console destination folders are selectable by admins, co-admins with reporting permissions, and group admins who can run reports.
  • Folder Insights and Content Insights are selectable by any user who can create those reports. Eligibility rules for those reports differ from Admin Console reports. See Folder Insights and Content Insights.

​
Admin Console reports

For reports you create from Admin Console > Reports, the Destination Folder field is in Run Settings and is pre-filled with Box Reports. You can keep that default or select a folder you own or co-own. You cannot save a report to an external folder.
Saving a report to a collaborated folder can expose the file to everyone who already has access to that folder, including people outside your enterprise. Folder icons in the picker display whether a folder is personal or collaborated. Use a personal folder when the report should stay private.
Legal Holds and Retention reports follow a different flow from Create Report and do not include a Destination Folder field.

​
Select a destination folder

  1. Create a report as described in Running reports.
  2. In Run Settings, find Destination Folder. It displays Box Reports by default.
  3. Select the Destination Folder field.
  4. In Select Destination Folder, browse from All Files or search by folder name or folder ID.
  5. Select the button next to the folder you want. You can select only one folder.
  6. Select Save.
  7. Finish configuring the report, then select Run. For a recurring report, schedule the report after you set the destination.
If you cannot browse to a nested folder you own or co-own, search for it by name or ID.

​
Folder types in the picker

Each row in Select Destination Folder includes a folder icon, the folder name, and a selectable button.

​
Folder Insights and Content Insights

You can select a destination folder when you create reports from Folder Insights or Content Insights. The folder must meet one of the following criteria:
  • You are the owner of the folder, or
  • You have an upload-capable permission level of Co-owner, Editor, Uploader, Viewer Uploader, or Previewer Uploader for the folder, and the folder owner is your Box admin.
Access can come from a direct collaboration or a group collaboration. If you do not select a destination folder, Box saves the report in your Box Reports folder.
The report file belongs to the user who requests it, even when it is saved to an admin-owned folder. That user must have enough available storage to accommodate the report file size, or the report cannot be created.
If your enterprise uses a closed folder structure with the Restrict Content Creation setting enabled, you must select a destination folder for the report. Destination folder eligibility follows the criteria above.

​
View path collaborations

If a collaboration on a nested folder has view path enabled (can_view_path=true), the report destination folder picker can display a parent folder at the root of All Files instead of the nested folder you were invited to. View path lets collaborators see the folder path without granting access to those parent folders. If that parent folder does not meet the destination folder criteria above, the picker filters it out. You cannot then browse to the nested folder, even when that nested folder is an eligible destination. To work around this:
  • In the folder picker, search by the nested folder name. Search can find and select the collaborated folder even when you cannot browse to it.
  • Update the collaboration to set can_view_path to false by using the Box API or Box CLI.
  • Remove and re-invite the collaborator without view path enabled.
  • Grant the user (or their group) direct access with an upload-capable role, such as Editor, on the parent folder that appears in the picker (so it is no longer filtered out), not only on the nested destination.
View path (can_view_path) often does not appear in the modern invite UI. Integrations, the Box API, and the Box CLI commonly set it. If you did not enable view path yourself, prefer search or granting access on the parent folder. Turning view path off hides that path from collaborators and can affect integrations that depend on it.
Last modified on October 27, 2026