Skip to main content
Users can select a destination folder for their report when creating reports from Folder Insights or Content Insights. The folder must meet one of the following criteria:
  • The user is the owner of the folder, or
  • The user has an upload-capable permission level of Co-owner, Editor, Uploader, Viewer Uploader, or Previewer Uploader for the folder, and the folder owner is their Box admin.
Access can come from a direct collaboration or a group collaboration. If a user does not select a destination folder, the report is saved in the user’s Box Reports folder by default.
The report file belongs to the user who requests it, even when it’s 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, users 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 show 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 August 20, 2026