To initiate a signature request in Box, you must have the download permissions to the file you send. Your collaborator role needs to be set as one of the following to send out a signature:
- Viewer Uploader
For more information on collaborator roles, visit: Understanding Collaborator Permission Levels.
File and Folder Permissions
The file for which you initiated sign request and a folder where a sign request will be saved might fall under restrictions, often security restrictions, such as one or more of these:
- Restrictive collaborator permissions are in place. For details, see Create Signature and Save Signature to a folder permissions in Understanding Collaborator Permission Levels.
- Classification label assigned to the content has the Box Sign Request restriction access policy defined.
- Malware scan detects threat within content and restricts downloads. For more information, see Shield Malware Detection.
- The file contains a watermark.
If such a file is restricted, continuing with the signature request may be prevented by the restriction, and you should work with your administrator to decide how best to proceed.
When a Sign request is triggered from a file in Box, or a file is uploaded to Box via Box Sign, Box prepares the document as a PDF. This PDF document then goes through the Sign workflow.
These PDF documents within the Box Sign workflow are always stored in Box, whether the workflow is completed or is in progress. The content within the Box Sign workflow is always protected in the same way as your other Box content.
After all recipients sign the document, Box creates the signed copy as a PDF with a digital certificate, and generates a unique hash from this PDF. Any changes made to the document after the signing process is closed can be detected by comparing hash codes.