End users who receive a File Request link may not know where the content and data they upload through the link is stored. They cannot see content uploaded by other users, and information about the File Request folder is not obviously visible in the preview experience. That’s why it’s important for your form to be clear, unambiguous, and organized. You may find it helpful to understand what the experience is like from your content submitter’s perspective. When people click the link you send out, a dedicated Web page opens. The page displays only your File Request form, exactly as you have built it. This is why it’s important to preview your form before sending out the link. (The exception would be if you’re creating an embed widget from your File Request, in which case it displays within a pre-configured web page.) The below image displays a simple File Request form – one upload zone and one field – with someone in the act of dragging a Word document into the upload zone.Documentation Index
Fetch the complete documentation index at: https://docs.box.com/llms.txt
Use this file to discover all available pages before exploring further.



- You cannot upload folders via the File Request form. You can only upload files.
- The size limit on uploaded files depends on the limit set by the requester’s enterprise.
- You can upload up to 500 files per submission.
- People who have access to a File Request link may view the folder owner’s metadata via the API, even if the metadata is not obviously visible in the preview experience.
- When Require uploaders to log in to Box is enabled, file request links embedded in external webpages cannot be loaded.