- Shield restrictions. If your files have more than one restriction, the most restrictive policy is used.
- For example: your Box file has a Print & Download restriction, while your destination folder has a No Box Sign restriction. You won’t be able to upload a local file, as the No Box Sign and Watermarking policies don’t allow for use of Box Sign for local files.
- A file must remain in the request. You can’t delete a file if it’s the only file in the request. To delete the file, you will need to upload another file to the request.
- No local files for replace. You can’t replace files with a local file. To use the file, upload it to Box first.
- Template sharing. To share a signature request with multiple files as a template, you need to share all files in the package first. To use the template, the user needs to have the minimum Viewer permissions enabled. If they need to rename or delete files, they should be granted Editor access. For more information on permissions, see Understanding Collaborator Permission Levels.
- Box Sign Report and User Activity are currently not supported. Events will be stored and backfilled. You can pull events from Streaming API with stream_type: admin_log.
- Lock on fields, but not files. If you replace a file with fewer pages, the fields are automatically placed on the last page. As a result, field placement will need to be re-adjusted accordingly. If the fields are locked, the template user won’t be able to move or add new fields to any newly added or replaced files.
To work with signature requests quickly and smoothly, especially for mobile users, we recommend keeping the total size of all files less than 25 MB.