- 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.
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 specify a destination folder for the report. The folder must either:
- Be owned by the user, or
- Be owned by their Box admin.
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:
- Update the collaboration to set
can_view_pathtofalseby 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 an eligible folder.
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.